Change batchGet to batch-get for casing consistency across AEP

[kjvalencik]

This PR updates AEP-0231 (Batch GET) to use batch-get instead of batchGet / BatchGet in HTTP URI custom method names. This ensures consistent kebab-case naming for custom methods across the AEP, aligning with the casing conventions used by other AEPs (e.g., AEP 122).

🍱 Types of changes

What types of changes does your code introduce to AEP? Put an x in the boxes
that apply

• Enhancement
• New proposal
• Migrated from google.aip.dev
• Chore / Quick Fix

📋 Your checklist for this pull request

Please review the AEP Style and Guidance for
contributing to this repository.

General

• Basic Guidance is met.
• Ensure that your PR
  references AEPs
  correctly.
• My code has been formatted
  (run make lint)

Open Questions

Currently api-linter will fail on batchGet custom methods. In my opinion, it's preferable to keep the linter and change the standard to use consistent kebab casing. However, if the current standard is intentional, the linter could be updated to understand the difference in convention for custom methods.

[rambleraptor]

Hi @kjvalencik! Thanks for the contribution. I think this seems very reasonable, especially considering we haven't gotten all of the batch APIs merged into the spec.

If you're not a member of the AEP Slack group, we'd love to have you! We're always looking to hear about how people are using/thinking about AEP in the real world

[kjvalencik]

Thanks for letting me know about the Slack group. I joined! We're early in our AEP adoption story, but we're pushing hard!