Export annotations

[mshima]

• move annotations a separate object to don’t mixup with other fields.
• move changelogDate to that annotation object

Maybe changelogDate should be kept at root and exported like an annotation as an exception.

Fixes #24262

---

Please make sure the below checklist is followed for Pull Requests.

• All continuous integration tests are green
• Tests are added where necessary
• The JDL part is updated if necessary
• jhipster-online is updated if necessary
• Documentation is added/updated where necessary
• Coding Rules & Commit Guidelines as per our CONTRIBUTING.md document are followed

When you are still working on the PR, consider converting it to Draft (below reviewers) and adding skip-ci label, you can still see CI build result at your branch.

[DanielFran]

@mshima when it export to jdl, it gives preference to annotations or not?

I mean if we have:

• dto mapstruct: it will export as dto mapstruct or @dto(mapstruct)?
• @dto(mapstruct): it will export as dto mapstruct or @dto(mapstruct)?

[mshima]

@DanielFran import/export is reproducible (order and presentation can change).

@ChangelogDate(123)
@Dto(custom)
entity A

dto A with mapstruct

Will become

@ChangelogDate("123")
@Dto("custom")
entity A

dto A with mapstruct

At generation time the annotation will override the option.
So dto custom will be used.

[mshima]

The old behavior is to mix annotations and options.
I don’t know which takes precedence.

annotations are exported as options if the annotation is an official option, ignored otherwise.