do not require aep resources have user-settable ids.

[toumorokoshi]

the create API optionally supports the ID field, but the aep requires it. it should be categorized as a "should".

blocks aep-dev/aepc#39

see: https://github.com/aep-dev/aepc/actions/runs/11624260167/job/32372581247?pr=39

example/bookstore/v1/bookstore.proto:360:1:create methods should contain a singular `string id` field. (buf-plugin-aep)

contingent on aep-dev/aeps#222 merging.

[rambleraptor]

This check is currently categorized as a "should", which means the check can be disabled by users.

There's two paths we have here:

1. Remove the check from the linter altogether.
2. Disable the check on your side.

What are your thoughts? Might be misunderstanding the ask.

[toumorokoshi]

ack! thank you. Let me look at disabling the check on my side.