change: bump version v2.12.0

[kolipakakondal]

Description

Please include a summary of the change and which issue is fixed.

Fixes # (IEP-XXX)

Type of change

Please delete options that are not relevant.

• Bug fix (non-breaking change which fixes an issue)
• New feature (non-breaking change which adds functionality)
• Breaking change (fix or feature that would cause existing functionality to not work as expected)
• This change requires a documentation update

How has this been tested?

Please describe the tests that you ran to verify your changes. Provide instructions so we can reproduce. Please also list any relevant details for your test configuration

• Test A
• Test B

Test Configuration:

• ESP-IDF Version:
• OS (Windows,Linux and macOS):

Dependent components impacted by this PR:

• Component 1
• Component 2

Checklist

• [ ] PR Self Reviewed
• [ ] Applied Code formatting
• [ ] Added Documentation
• [ ] Added Unit Test
• [ ] Verified on all platforms - Windows,Linux and macOS

Summary by CodeRabbit

• New Features

  • Upgraded the product to version 2.12.0, indicating new features and improvements.

• Documentation

  • Updated product metadata to reflect the new version and repository details.

[coderabbitai[bot]]

Walkthrough

The changes indicate a version upgrade for an Espressif IDF bundle and its associated product configuration. The bundle version has been incremented from 2.11.1 to 2.12.0, suggesting new features or fixes. Additionally, the product configuration now specifies its type as "features" and includes empty "name" attributes for repository elements, possibly in preparation for future repository identification.

Changes

File Path	Change Summary
.../idf.branding/META-INF/MANIFEST.MF	Bundle-Version updated from 2.11.1.qualifier to 2.12.0.qualifier.
releng/com.espressif.idf.product/idf.product	Product version updated from "2.11.1" to "2.12.0"; added "type" attribute with value "features"; added empty "name" attributes to <repository> elements.

🐇✨ A hop of version, a leap in the code, From 2.11 to 2.12, the changes forebode. New features to discover, bugs left behind, A rabbit's delight in the progress we find. 🚀🌟

Thank you for using CodeRabbit. We offer it for free to the OSS community and would appreciate your support in helping us grow. If you find it useful, would you consider giving us a shout-out on X ?

---

Tips

### Chat with CodeRabbit Bot (`@coderabbitai`) - You can reply to a review comment made by CodeRabbit. - You can tag CodeRabbit on specific lines of code or files in the PR by tagging `@coderabbitai` in a comment. - You can tag `@coderabbitai` in a PR comment and ask one-off questions about the PR and the codebase. Use quoted replies to pass the context for follow-up questions. ### CodeRabbit Commands (invoked as PR comments) - `@coderabbitai pause` to pause the reviews on a PR. - `@coderabbitai resume` to resume the paused reviews. - `@coderabbitai review` to trigger a review. This is useful when automatic reviews are disabled for the repository. - `@coderabbitai resolve` resolve all the CodeRabbit review comments. - `@coderabbitai help` to get help. Additionally, you can add `@coderabbitai ignore` anywhere in the PR description to prevent this PR from being reviewed. ### CodeRabbit Configration File (`.coderabbit.yaml`) - You can programmatically configure CodeRabbit by adding a `.coderabbit.yaml` file to the root of your repository. - The JSON schema for the configuration file is available [here](https://coderabbit.ai/integrations/coderabbit-overrides.v2.json). - If your editor has YAML language server enabled, you can add the path at the top of this file to enable auto-completion and validation: `# yaml-language-server: $schema=https://coderabbit.ai/integrations/coderabbit-overrides.v2.json`