Missing AEP Rule Implementations in aep-e2e-validator

[rambleraptor]

Missing AEP Rule Implementations in aep-e2e-validator

This issue tracks AEPs that currently lack implementation in the aep-e2e-validator repository, focusing on rules that require runtime verification.

The following AEPs need to be implemented or have their runtime validation aspects addressed:
(This list was generated by Gemini)

• AEP-131 (Get): Verify standard behavior, such as returning NOT_FOUND for non-existent resources (often implicitly tested, but missing explicit suite).
• AEP-136 (Custom Methods): Verify standard custom methods (e.g., Rename, Move) adhere to their defined behaviors.
• AEP-137 (Apply): Verify the logic of the Apply pattern (state transitions and idempotency).
• AEP-154 (Preconditions): Verify that requests fail with ABORTED or FAILED_PRECONDITION when If-Match (ETag) checks fail.
• AEP-160 (Filtering): Verify that the filter parameter actually filters the returned list results correctly.
• AEP-161 (Field Masks): Verify that read_mask limits the response and update_mask limits the side effects of updates.
• AEP-193 (Errors): Verify that the API returns the correct gRPC status codes and error details for various failure scenarios.
• AEP-211 (Authorization): Verify access control behavior (e.g., returning NOT_FOUND instead of PERMISSION_DENIED when appropriate to hide existence).
• AEP-217 (Unreachable Resources): Verify that the unreachable list is populated when specific backends are unavailable.
• AEP-231, 233, 234, 235 (Batch Methods): Verify atomicity (if applicable) and partial failure reporting in batch operations.