FED-2854 Fix num keys incorrectly linting as not unique

[greglittlefield-wf]

Motivation

Setting a key to a value that has a static type of num incorrectly lints as a non-unique key.

..key = aNum
//      ^^^^
// over_react_object_to_string_as_key: Keys shouldn't be derived from 'num.toString()' since the value is the same for all instances. 

This bug is caused by us having cases for int and double, but not for num.

Changes

• Add case for num type
• Add regression test

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:
    • Verify regression test fails in the commit before the fix was added, and passes on latest commit (i.e., CI passes for this PR)
  • 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 Frontend Frameworks Design 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.

[sydneyjodon-wk]

+10 🎉

• Verify regression test fails in the commit before the fix was added, and passes on latest commit (i.e., CI passes for this PR)

@Workiva/release-management-p

[rmconsole-wf]

+1 from RM