deps: Update osgi.annotation dependency to 8.1.0

[bjhargrave]

Version 8.1.0 removes the use of enum types in the annotations which
avoids compiler warnings for downstream users of the api jar.

We also include osgi.annotation in the tck project to make the
annotation classes available to javadoc to avoid warnings.

[bjhargrave]

@Emily-Jiang This addresses the compiler warning issue in #716.

[radcortez]

Great. Thank you!

[radcortez]

I believe this should be backported to 2.x.

[bjhargrave]

I believe this should be backported to 2.x.

I can make a PR for that. What branch?

[radcortez]

I believe this should be backported to 2.x.

I can make a PR for that. What branch?

We don't have one. Let me create one. Thanks!

[radcortez]

This should cover it: https://github.com/eclipse/microprofile-config/tree/2.x

[Emily-Jiang]

Thank you @bjhargrave !

[Emily-Jiang]

@radcortez we can do a service release once @bjhargrave makes a PR against 2.x.

[brunolmfg]

Unfortunately that fix was merged into master after the 3.0.x was branched. So the version 3.0.2 doesn't contain the upgrade of osgi.annotation to 8.1.0.

Looking in the history I've notice some confusing versioning:

• 3361745: 3.0 tagged;
• 66b9611: 3.0.1 tagged a first time;
• d4a6e84: 3.0.x branched;
• 8f2df48: 3.0.1 tagged again in master;
• 18d1b92: The fix merged in master;
• 19ca7d8: 3.0.2 tagged in 3.0.x branch.

@radcortez, @bjhargrave and @Emily-Jiang I believe this should be backported to 3.0.x.

@turing85 It seems to me that the problem you posted on Quarkus Zulip is due to the upgrade of MP Config from 2.0.1 (osgi.annotation fixed) to 3.0 (osgi.annotation not fixed) present in Quarkus 3.0.0.Alpha1 and later.

[radcortez]

We need to do a release to fix other stuff, so we might as well just release it as is and let consumers update to the new version.