[DRAFT] Core Integration

[TreyWW]

Description

This PR will separate the project and have a separate core module (app). This will contain things like base templates, settings, and other shared utils.

Checklist / reminders

• add back Receipt signals
• add back billing signals that are finance related
• add backcore\src\core\backend_utils\api\settings\defaults.py but only on MF
• add back core\src/core/backend_utils/service/defaults/get.py but only on MF
• add back src/core/backend_utils/api/settings/email_templates.py defaults and src/core/backend_utils/service/settings/view.py
• add back api public endpoints for MF (clients, finance)
• add back management/scheduled_tasks for MF
• add back boto3 scheduler service for MF
• add back core\backend_utils\webhooks for MF
• add back modal (base/urls.py and modal.py) on core and MF
• add back api/emails/send.py and in urls.py
• add back src/core/backend_utils/api/maintenance/now.py
• add back email_waitlist to CORE (requires BOTO3 back first in CORE)

Related PRs, Issues etc

This is instead of an identity solution like below. Decided an app integration would be more ideal than separate identity servers for this scale.

• Related Issue Identity Integration #537
• Closes Identity Integration #537

[github-actions]

Dependency Review

The following issues were found:

• ✅ 0 vulnerable package(s)
• ✅ 0 package(s) with incompatible licenses
• ✅ 0 package(s) with invalid SPDX license definitions
• ⚠️ 14 package(s) with unknown licenses.
• ⚠️ 22 packages with OpenSSF Scorecard issues.

View full job summary

[TreyWW]

On hold awaiting for cookie sharing between both so sessions dont log out every time you go to another site using the same shared DB.

[TreyWW]

Fixed session issue with a full cache + DNS reset.

Currently stuck with deciding how to proceed as this will either need a custom migration or require users to manually copy over wanted data to a new schema.