[BUMP] Update dependency @ember/string to v4 (junior)

[renovate]

This PR contains the following updates:

Package	Change	Age	Adoption	Passing	Confidence
@ember/string	^3.1.1 -> ^4.0.0

---

Configuration

📅 Schedule: Branch creation - "every 1 hour every weekday" (UTC), Automerge - At any time (no schedule defined).

🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.

♻ Rebasing: Never, or you tick the rebase/retry checkbox.

🔕 Ignore: Close this PR and you won't be reminded about this update again.

---

• If you want to rebase/retry this PR, check this box

---

This PR was generated by Mend Renovate. View the repository job log.

[renovate]

⚠️ Artifact update problem

Renovate failed to update an artifact related to this branch. You probably do not want to merge this PR as-is.

♻ Renovate will retry this branch, including artifacts, only when one of the following happens:

• any of the package files in this branch needs updating, or
• the branch becomes conflicted, or
• you click the rebase/retry checkbox if found above, or
• you rename this PR's title to start with "rebase!" to trigger it manually

The artifact failure details are included below:

File name: junior/package-lock.json

npm error code ERESOLVE
npm error ERESOLVE could not resolve
npm error
npm error While resolving: @ember-data/[email protected]
npm error Found: @ember/[email protected]
npm error node_modules/@ember/string
npm error   dev @ember/string@"^4.0.0" from the root project
npm error
npm error Could not resolve dependency:
npm error peer @ember/string@"^3.1.1" from @ember-data/[email protected]
npm error node_modules/@ember-data/model
npm error   peerOptional @ember-data/model@"*" from [email protected]
npm error   node_modules/ember-cli-mirage
npm error     dev ember-cli-mirage@"^3.0.3" from the root project
npm error   @ember-data/model@"5.3.3" from [email protected]
npm error   node_modules/ember-data
npm error     dev ember-data@"~5.3.3" from the root project
npm error     1 more (ember-cli-mirage)
npm error
npm error Conflicting peer dependency: @ember/[email protected]
npm error node_modules/@ember/string
npm error   peer @ember/string@"^3.1.1" from @ember-data/[email protected]
npm error   node_modules/@ember-data/model
npm error     peerOptional @ember-data/model@"*" from [email protected]
npm error     node_modules/ember-cli-mirage
npm error       dev ember-cli-mirage@"^3.0.3" from the root project
npm error     @ember-data/model@"5.3.3" from [email protected]
npm error     node_modules/ember-data
npm error       dev ember-data@"~5.3.3" from the root project
npm error       1 more (ember-cli-mirage)
npm error
npm error Fix the upstream dependency conflict, or retry
npm error this command with --force or --legacy-peer-deps
npm error to accept an incorrect (and potentially broken) dependency resolution.
npm error
npm error
npm error For a full report see:
npm error /tmp/renovate/cache/others/npm/_logs/2024-07-30T01_53_34_151Z-eresolve-report.txt
npm error A complete log of this run can be found in: /tmp/renovate/cache/others/npm/_logs/2024-07-30T01_53_34_151Z-debug-0.log

[pix-bot-github]

Une fois les applications déployées, elles seront accessibles via les liens suivants :

• App (.fr)
• App (.org)
• Orga (.fr)
• Orga (.org)
• Certif (.fr)
• Certif (.org)
• Junior
• Admin
• API
• Audit Logger

Les variables d'environnement seront accessibles via les liens suivants :

• scalingo front
• scalingo api
• scalingo audit-logger

[renovate]

Renovate Ignore Notification

Because you closed this PR without merging, Renovate will ignore this update. You will not get PRs for any future 4.x releases. But if you manually upgrade to 4.x then Renovate will re-enable minor and patch updates automatically.

If you accidentally closed this PR, or if you changed your mind: rename this PR to get a fresh replacement PR.