chore: add custom annotation class

[nankolena]

Linked issue(s)

Resolves KOL-7552

What change does this PR introduce and why?

Created a class for custom annotation. See this comment for verification steps.

Screenshots of generated API ref:

Please check if the PR fulfills these requirements

• Include reference to internal ticket and/or GitHub issue "Fixes #NNNN" (if applicable)
• Relevant tests for the changes have been added
• Relevant docs have been added / updated

[millerpeterson]

Should there be some additional general indication that additional fields might be present on the objects depending on kind?

[nankolena]

Should there be some additional general indication that additional fields might be present on the objects depending on kind?

Technically in the case of bev, we do need the locator field. I intentionally left it generic with Please reach out to the Kolena team for support if you need custom annotations because the immediate implementation is for a specific customer and did not want to give the expectations that it will work out of the box for everyone if they use the same kind. Let me know what you think on this

[millerpeterson]

I intentionally left it generic with Please reach out to the Kolena team for support if you need custom annotations because the immediate implementation is for a specific customer and did not want to give the expectations that it will work out of the box for everyone if they use the same kind.

Yeah that makes sense to me 👍