Upgrade json_serializable version to permit analyzer 2.0 usage

[alanknight-wk]

Motivation

By upgrading the json_serializable requirement to 5.0.0, we can support analyzer 2.0

Changes

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:
  • [ ] 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

[aviary3-wk]

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.

[coreysprague]

Any update on this? Would love to see this get merged and published. It's the one dependency we have that is holding back a slew of other transitive dependencies (they've all since switched to analyzer 2.*)

[alanknight-wk]

It's complicated. Like, 7 intermediate milestones complicated. https://wiki.atl.workiva.net/display/CP/Dependency+Upgrades

This should probably just get closed for the moment.