fix: update getSymbols in NumberParser to support roundingIncrement

[snowystinger]

Closes #7168

✅ Pull Request Checklist:

• Included link to corresponding React Spectrum GitHub Issue.
• Added/updated unit tests and storybook for this change (for new code or code which already has tests).
• Filled out test instructions.
• Updated documentation (if it already exists for this component).
• Looked at the Accessibility Practices for this feature - Aria Practices

📝 Test Instructions:

🧢 Your Project:

[rspbot]

Build successful! 🎉

• View the storybook
• View the storybook-19
• View the storybook-17
• View the storybook-16
• View the S2 storybook
• View the documentation

[devongovett]

Assuming that none of these options affect the result? e.g. if the user passed in different values in intlOptions this would override.

[snowystinger]

Right, this is only to get possible symbols. By overriding these with the defaults we get possibly a few extra symbols that aren't possible with the users options, but that won't hurt anything.

I do not believe that any combination of these three options will add additional symbols. Though it is an assumption that I've made based on: it has worked like this for 4 years before Chrome added these values into the resolvedOptions.