chore(deps): update dependency stimulus to v3

[renovate]

This PR contains the following updates:

Package	Change	Age	Adoption	Passing	Confidence
stimulus	2.0.* -> 3.2.*

---

Configuration

📅 Schedule: Branch creation - At any time (no schedule defined), Automerge - At any time (no schedule defined).

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

♻ Rebasing: Whenever PR becomes conflicted, 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.

[guardrails]

⚠️ We detected 13 security issues in this pull request:

Hard-Coded Secrets (1)

Severity	Details	Docs
Medium	Title: Secret Keyword https://github.com/koromerzhin/labstag/blob/695a0f870feb1542bf8f1f5c9df655dfebc62310/docker-compose-lampy.yml#L24	📚

More info on how to fix Hard-Coded Secrets in General.

---

Vulnerable Libraries (12)

Severity	Details
High	korojscommands@1.2.18 upgrade to: >=0.1.0
High	libnpmaccess@3.0.2 (t) upgrade to: >3.0.2
High	libnpmhook@5.0.3 (t) upgrade to: >5.0.3
High	libnpmorg@1.0.1 (t) upgrade to: >1.0.1
High	libnpmpublish@1.1.3 (t) upgrade to: >2.0.0
High	libnpmsearch@2.0.2 (t) upgrade to: >2.0.2
High	libnpmteam@1.0.2 (t) upgrade to: >1.0.2
High	npm-profile@4.0.4 (t) upgrade to: >4.0.4
Medium	semantic-git-commit-cli@3.7.0 (t) upgrade to: >=1.1.0
Medium	blamer@1.0.1 (t) upgrade to: >1.0.1
Medium	npm-lifecycle@3.1.5 (t) upgrade to: >=2.0.0
Medium	yaml@2.2.1 (t) upgrade to: >2.2.1

More info on how to fix Vulnerable Libraries in JavaScript.

---

👉 Go to the dashboard for detailed results.

📥 Happy? Share your feedback with us.

[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: package-lock.json

npm ERR! code ERESOLVE
npm ERR! ERESOLVE could not resolve
npm ERR! 
npm ERR! While resolving: @symfony/stimulus-bridge@2.0.2
npm ERR! Found: stimulus@3.2.1
npm ERR! node_modules/stimulus
npm ERR!   dev stimulus@"3.2.*" from the root project
npm ERR! 
npm ERR! Could not resolve dependency:
npm ERR! peer stimulus@"^2.0" from @symfony/stimulus-bridge@2.0.2
npm ERR! node_modules/@symfony/stimulus-bridge
npm ERR!   dev @symfony/stimulus-bridge@"2.0.*" from the root project
npm ERR! 
npm ERR! Conflicting peer dependency: stimulus@2.0.0
npm ERR! node_modules/stimulus
npm ERR!   peer stimulus@"^2.0" from @symfony/stimulus-bridge@2.0.2
npm ERR!   node_modules/@symfony/stimulus-bridge
npm ERR!     dev @symfony/stimulus-bridge@"2.0.*" from the root project
npm ERR! 
npm ERR! Fix the upstream dependency conflict, or retry
npm ERR! this command with --force, or --legacy-peer-deps
npm ERR! to accept an incorrect (and potentially broken) dependency resolution.
npm ERR! 
npm ERR! See /tmp/worker/dcf200/fd71a1/cache/others/npm/eresolve-report.txt for a full report.

npm ERR! A complete log of this run can be found in:
npm ERR!     /tmp/worker/dcf200/fd71a1/cache/others/npm/_logs/2023-06-18T06_16_41_364Z-debug-0.log

[gitguardian]

️✅ There are no secrets present in this pull request anymore.

If these secrets were true positive and are still valid, we highly recommend you to revoke them.
Once a secret has been leaked into a git repository, you should consider it compromised, even if it was deleted immediately.
Find here more information about risks.

---

<sup><sub>🦉 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!</sub></sup>

[renovate]

Edited/Blocked Notification

Renovate will not automatically rebase this PR, because it does not recognize the last commit author and assumes somebody else may have edited the PR.

You can manually request rebase by checking the rebase/retry box above.

⚠ Warning: custom changes will be lost.