Copy language version comments to generated part files

[greglittlefield-wf]

Motivation

Libraries with language version comments must have the same version comments in all of their part files.

As a result, it's currently impossible to add a language version comment to a file with a generated over_react part, since the generated part never includes a language version comment.

Changes

• Copy any language version comment from the source file to the generated over_react part file.

Release Notes

Review

See CONTRIBUTING.md for more details on review types (+1 / QA +1 / +10) and code review process.

Please review:

QA Checklist

• Tests were updated and provide good coverage of the changeset and other affected code
• Manual testing was performed if needed
  • Steps from PR author:
    • Add a language version comment to an example file with a generated over_react part
    • Run a build (reminder you can run pub run build_runner --build-filter='**.g.dart' to build only Dart files and not JS
    • Verify that the language version comment is present in the generated file
  • Anything falling under manual testing criteria outlined in CONTRIBUTING.md

Merge Checklist

While we perform many automated checks before auto-merging, some manual checks are needed:

• A Client Platform member has reviewed these changes
• There are no unaddressed comments - this check can be automated if reviewers use the "Request Changes" feature
• For release PRs - Version metadata in Rosie comment is correct

[aviary2-wf]

Security Insights

No security relevant content was detected by automated scans.

Action Items

• Review PR for security impact; comment "security review required" if needed or unsure
• Verify aviary.yaml coverage of security relevant code

---

Questions or Comments? Reach out on Slack: #support-infosec.

[robbecker-wf]

I tested this on wdesk and it indeed copied the language version correctly

[aaronlademann-wf]

+1

@Workiva/release-management-pp

[rmconsole-wf]

+1 from RM