ci(dependabot): update to group dependabot PRs and limit only to secu…

[tomassebestik]

Description

This changes the Dependabot settings to:

• Create a PR only for security updates.
• Group all dependency updates into a single PR.
• Set the commit message to follow the conventional and Espressif standard format: ci(deps-xxx): [skip ci] <message-subject>.
• Add the [skip ci] marker to the commit message to skip CI (pre-commit / danger can fail).

Links to GitHub Dependabot docs:

• https://docs.github.com/en/code-security/dependabot/dependabot-version-updates/configuration-options-for-the-dependabot.yml-file
• https://docs.github.com/en/code-security/dependabot/dependabot-security-updates/configuring-dependabot-security-updates

[github-actions]

	Messages
📖	🎉 Good Job! All checks are passing!

👋 Hello tomassebestik, we appreciate your contribution to this project!

---

📘 Please review the project's Contributions Guide for key guidelines on code, documentation, testing, and more.

---

Click to see more instructions ...

This automated output is generated by the PR linter DangerJS, which checks if your Pull Request meets the project's requirements and helps you fix potential issues.

DangerJS is triggered with each push event to a Pull Request and modify the contents of this comment.

Please consider the following:
- Danger mainly focuses on the PR structure and formatting and can't understand the meaning behind your code or changes.
- Danger is not a substitute for human code reviews; it's still important to request a code review from your colleagues.
- To manually retry these Danger checks, please navigate to the Actions tab and re-run last Danger workflow.

Review and merge process you can expect ...

We do welcome contributions in the form of bug reports, feature requests and pull requests.

1. An internal issue has been created for the PR, we assign it to the relevant engineer.
2. They review the PR and either approve it or ask you for changes or clarifications.
3. Once the GitHub PR is approved we do the final review, collect approvals from core owners and make sure all the automated tests are passing.
- At this point we may do some adjustments to the proposed change, or extend it by adding tests or documentation.
4. If the change is approved and passes the tests it is merged into the default branch.

Generated by 🚫 dangerJS against e581e2f

[tomassebestik]

@kumekay @hfudev PTAL ... if you have another prooven way how to set this, please let me know

[github-actions]

This PR is stale because it has been open 30 days with no activity. Remove Status: Stale label or comment or this will be closed in 7 days.

[github-actions]

This PR was closed because it has been stalled for 10 days with no activity.