Fix so that the normalizer retains the read/write only attribute

[Mattias-Sehlstedt]

Fixes #21732.

I have added so that it keeps ReadOnly and WriteOnly, but it might be that one should even run copyMetadata?

PR checklist

• Read the contribution guidelines.
• Pull Request title clearly describes the work in the pull request and Pull Request description provides details about how to validate the work. Missing information here may result in delayed response from the community.
• Run the following to build the project and update samples:

  ./mvnw clean package || exit
  ./bin/generate-samples.sh ./bin/configs/*.yaml || exit
  ./bin/utils/export_docs_generators.sh || exit
  

  (For Windows users, please run the script in WSL)
  Commit all changed files.
  This is important, as CI jobs will verify all generator outputs of your HEAD commit as it would merge with master.
  These must match the expectations made by your contribution.
  You may regenerate an individual generator by passing the relevant config(s) as an argument to the script, for example ./bin/generate-samples.sh bin/configs/java*.
  IMPORTANT: Do NOT purge/delete any folders/files (e.g. tests) when regenerating the samples as manually written tests may be removed.
• File the PR against the correct branch: master (upcoming 7.x.0 minor release - breaking changes with fallbacks), 8.0.x (breaking changes without fallbacks)
• If your PR solves a reported issue, reference it using GitHub's linking syntax (e.g., having "fixes #123" present in the PR description)
• If your PR is targeting a particular programming language, @mention the technical committee members, so they are more likely to review the pull request.

[wing328]

but it might be that one should even run copyMetadata?

what do you mean by that? do you mean we should also handle other meta data in addition to readonly, writeonly?

[Mattias-Sehlstedt]

but it might be that one should even run copyMetadata?

what do you mean by that? do you mean we should also handle other meta data in addition to readonly, writeonly?

I was just wondering, without putting too much thought into it, whether there are additional attributes that might be relevant to keep when doing the normalization.

[Mattias-Sehlstedt]

Converted to draft since I see now that this not really represent the issue reported, will look further into it.

[robotmrv]

@Mattias-Sehlstedt @wing328
what was the reason you did not use ModelUtils#copyMetadata() ?
I have an issue that e.g. I lose descrption from property level, and most like it is not only description but all except attributes copied in this PR

[Mattias-Sehlstedt]

Since there was no discussion regarding my speculation on whether it was relevant to do copyMetadata, I though it easiest to only adjust for the reported issue. This since I cannot myself state that I am certain that everything from copyMetadata is relevant and correct.

But if you have further issues with metadata propagation, I believe it would be best to raise an issue for that and exemplify what data that is "lost".