[HGI 404] update pinned version of sentry to 7.45.0

[AnkitUnthinkable]

What does this PR do?

In this PR includes

1. sentry update from version 5.12.1 to 7.45.0 (latest).
2. We are using pluggable integrations RewriteFrame which is also getting updated from 5.12.1 to 7.45.0 (latest).
3. Sentry options whitelistURLs and blacklistURLs are changed to allowURLs and denyURLs.
4. Sentry options serverName and maxMessageLength is no longer available.

Testing Docs: https://paper.dropbox.com/doc/Sentry-version-upgrade-v5.12.1-to-v7.45.0-Testing-Docs.--B2Jx3D2y_~_YtsXrYJ1W1sssAQ-hdyjHRh7cPrSg7AoMg66Y

Testing

Testing completed successfully in localhost

Jira tickets:
https://segment.atlassian.net/browse/HGI-404?atlOrigin=eyJpIjoiMGVmZDgwYWExMWI2NGNjNThmZjhmZTc3ZWYwM2FjNzMiLCJwIjoiaiJ9

PREVIOUS VERSION

Current Version

[varadarajan-tw]

Can we ensure test cases are updated? Also, since this is a major version upgrade, can we confirm all fields and settings are working as expected?.

[varadarajan-tw]

Testing Doc - https://paper.dropbox.com/doc/Sentry-version-upgrade-v5.12.1-to-v7.45.0-Testing-Docs.--B2Jx3D2y_~_YtsXrYJ1W1sssAQ-hdyjHRh7cPrSg7AoMg66Y

[varadarajan-tw]

Left few more questions and comments

[varadarajan-tw]

The changes look good!
We are deprecating two settings

1. ServerName - It was never supported for browser SDK by Sentry
2. MaxMessageLength - It was already unsupported in the previous version this destination was on.

@brennan - Any thoughts on whether to delete such deprecated settings from partner portal or just add deprecation warning and leave it as such?
Note: There is no cloud mode destination for Sentry.

[brennan]

Hey @varadarajan-tw - I'm a fan of deprecating settings- as long as we test first in stage b/c we don't have a specific process for deprecating or removing settings other than simply deleting from partner portal. Simply deleting them from partner portal should be ok, so long as we're not doing any operations on the setting in integrations-consumer or the monoservice, e.g. ServerName.length or something.

tl;dr - it's ok to leave them, but if there is time, it may be a good opportunity to document a process for removing deprecated settings. If so, then we should document and remove these.