Now write default annotation values to adapter Attributes

[SentryMan]

now attributes should work as expected

[rob-bygrave]

Oh wow - very cool !!! member::getDefaultValue ... I didn't even look for that - nice !!

[SentryMan]

The Annotation Mirror API is pretty arcane I would say, now I just gotta fix these tests

[rob-bygrave]

expected: "size must be between 2 and 4"
 but was: "{jakarta.validation.constraints.Size.message}"

Ah, this looks like the one default value that we didn't want it seems. Edit: But maybe we want it on custom validators in the future ...

[SentryMan]

it's possible some may want to use the same jakarta properties yeah

[rob-bygrave]

same jakarta properties

Not really or at least this is not the case for the Jakarta validator that we support out of the box. All of those ones will use the {avaje...} resource bundle keys [except I'm also looking to tweak for DecimalMax based on the inclusive flag in order that we have NO Expression Language use in the messages / so our message interpolation is just simple token replacement only].

So for example, in BasicAdapters these are all going to translate to {avaje...} ... I could probably do the change for this I think so our tests pass.

[SentryMan]

were we not going to give the ability to specify what resource bundle path to use? If we have that there is no need to modify it too much.

[SentryMan]

but feel free to modify the PR

[rbygrave]

Ok, I'll merge this in. I intentionally left out the .validation.constraints. from the keys so I'll revert that part of the change back.