INTL-1677: Exclude Pendo ID pattern in codemod

[alanknight-wk]

Motivation

Exclude Pendo IDs, or similar from conversion. Those are of the form Period.Separated.Uppercase.Words

Changes

• It turns out that our existing check for CamelCaseWords wasn't actually working. Or at least it was checking for quoted strings, meaning e.g. var foo = "'stuff'". Which are extremely rare. I didn't think this made any sense at all, so I just dropped the "quoted" requirement and allowed periods within the word. It also had no tests, so it's hard to know what the intent was. Added some tests.
• We also weren't using the checks for strings to exclude in the constant string migrator, so I started including them.
• We used strings that we expected to be converted in test cases, which met the camel case requirement (if we didn't have quotes), specifically 'testString1', 'testString2'. I turned those into 'test String 1' and 2.
• There were a number of regular expressions used in utils.dart which were being recreated every time through the method. Regular expressions are relatively expensive to initialize, so I pulled them out into variables.
• The camel case check is done via a very large RegExp. I considered rewriting it, but the logic is fairly complicated, so I settled for writing an extensive comment.

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 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

[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.

[alanknight-wk]

@Workiva/release-management-p

[rmconsole-wf]

+1 from RM