chore: V2 core loader + modules integration-tests

[olivermrbl]

What

• Create integration-tests/modules
• Move V2 modules integration tests from plugins to modules
• Introduce V2 core loader

🚧 Important change

The introduction of the V2 core loader will mean the following are no longer loaded/registered:

• Core services
• Core repositories
• Core strategies
• Core defaults
• Core models
• Passport
• Typeorm DB connection
• Search Index
• Plugins

To add on approval: GitHub Action step

[changeset-bot]

🦋 Changeset detected

Latest commit: 67d229a

The changes in this PR will be included in the next version bump.

This PR includes changesets to release 1 package

Name	Type
@medusajs/medusa	Minor

Not sure what this means? Click here to learn what changesets are.

Click here if you're a maintainer who wants to add another changeset to this PR

[vercel]

The latest updates on your projects. Learn more about Vercel for Git ↗︎

Name	Status	Preview	Comments	Updated (UTC)
medusa-dashboard	✅ Ready (Inspect)	Visit Preview	💬 Add feedback	Feb 29, 2024 3:20pm

3 Ignored Deployments

Name	Status	Preview	Comments	Updated (UTC)
api-reference	⬜️ Ignored (Inspect)			Feb 29, 2024 3:20pm
docs-ui	⬜️ Ignored (Inspect)	Visit Preview		Feb 29, 2024 3:20pm
medusa-docs	⬜️ Ignored (Inspect)	Visit Preview		Feb 29, 2024 3:20pm

[riqwan]

🔥

[srindom]

LGTM!

[gitguardian]

⚠️ GitGuardian has uncovered 3 secrets following the scan of your pull request.

Please consider investigating the findings and remediating the incidents. Failure to do so may lead to compromising the associated services or software components.

🔎 Detected hardcoded secrets in your pull request

GitGuardian id	GitGuardian status	Secret	Commit	Filename
9679163	Triggered	Generic Password	67d229a	.github/workflows/action.yml	View secret
9679163	Triggered	Generic Password	67d229a	.github/workflows/action.yml	View secret
9679163	Triggered	Generic Password	67d229a	.github/workflows/action.yml	View secret

🛠 Guidelines to remediate hardcoded secrets

1. Understand the implications of revoking this secret by investigating where it is used in your code.
2. Replace and store your secrets safely. Learn here the best practices.
3. Revoke and rotate these secrets.
4. If possible, rewrite git history. Rewriting git history is not a trivial act. You might completely break other contributing developers' workflow and you risk accidentally deleting legitimate data.

To avoid such incidents in the future consider

• following these best practices for managing and storing secrets including API keys and other credentials
• install secret detection on pre-commit to catch secret before it leaves your machine and ease remediation.

---

<sup>🦉 GitGuardian detects secrets in your source code to help developers and security teams secure the modern development process. You are seeing this because you or someone else with access to this repository has authorized GitGuardian to scan your pull request.

Our GitHub checks need improvements? Share your feedbacks!</sup>