Move app instances into their respective modules

[dcramer]

Result of playing around with the idea of killing off sentry.app

The monstrous hack of LazyBackendWrapper has benefits that its much easier to do module level imports (where we can't today due to circular imports).

As a followup we should:

• move sentry.utils.locking into sentry.locks
• rename sentry.ratelimiter to sentry.ratelimits
• create a base Service class which manages enabled() and validate() core methods
• add a basic service registry to aid with things like "validate all services" (this might be able to use the provider code)

#nochanges

[getsentry-bot]

	1 Warning
⚠️	Changes require @getsentry/security sign-off

Security concerns found

• src/social_auth/init.py
• src/social_auth/backends/pipeline/user.py
• src/social_auth/fields.py
• src/sentry/web/frontend/accounts.py

Generated by 🚫 danger

[dcramer]

DONT WORRY! Its only like 500 lines changed... across 65 files.

[mitsuhiko]

Seems good but i want to play around if the expose can be done better.

[dcramer]

tests pass in sentry + getsentry, and some minor QA (clicking UI, workers doing work) seems to indicate things are good

[dcramer]

gotta reimplement this real quick

[dcramer]

resolved

[dcramer]

getting a few more quick tests in place then will get this merged

[mattrobenolt]

Nothing at all could go wrong here. 🥇