fix: byTranslationKey() for multi-key schemas without translations.txt support

[bdferris-v2]

The @PrimaryKey(translationRecordIdType) field is used to indicated which keys, if any, for a given GTFS entity can be used for performing translations.txt lookups via byTranslationKey() methods generated in the table container. Currently, code in TableContainerIndexGenerator will generate an implementation for byTranslationKey() even if none of the @PrimaryKey fields have been marked as the translation RECORD_ID. This can lead to some weird behavior where the method will return a value even if none should be returned or generate code that does not actually compile.

This PR fixes this behavior by no longer generating a byTranslationKey() implementation if the entity type does not support. Instead, empty is returned.

Please make sure these boxes are checked before submitting your pull request - thanks!

• Run the unit tests with gradle test to make sure you didn't break anything
• Format the title like "feat: [new feature short description]". Title must follow the Conventional Commit Specification(https://www.conventionalcommits.org/en/v1.0.0/).

[asvechnikov2]

LGTM!

[github-actions]

✅ Rule acceptance tests passed.
New Errors: 0 out of 1374 datasets (~0%) are invalid due to code change, which is less than the provided threshold of 1%.
Dropped Errors: 0 out of 1374 datasets (~0%) are invalid due to code change, which is less than the provided threshold of 1%.
0 out of 1374 sources (~0 %) are corrupted.
Commit: d7d845c
Download the full acceptance test report here (report will disappear after 90 days).
✅ Rule acceptance tests passed.