Workspace: add BlazeResolveConfigurationID to map OCResolveConfigurations to azel configurations

[LeFrosch]

No description provided.

[gemini-code-assist]

Summary of Changes

Hello, I'm Gemini Code Assist¹! I'm currently reviewing this pull request and will post my feedback shortly. In the meantime, here's a summary to help you and other reviewers quickly get up to speed!

This pull request refactors the handling of configuration identifiers within the Blaze plugin for CLion. By introducing a dedicated BlazeResolveConfigurationID class, it establishes a more robust and explicit mechanism for mapping internal Blaze configuration data to CLion's OCResolveConfiguration unique IDs. This change streamlines configuration lookup and creation, improving the clarity and maintainability of the configuration management logic.

Highlights

• New Configuration ID Class: Introduced BlazeResolveConfigurationID to provide a standardized, unique identifier for Blaze resolve configurations, facilitating consistent mapping.
• Simplified Configuration Retrieval: Updated BlazeConfigurationData.get to accept a String configurationId directly, simplifying the process of retrieving Blaze configurations.
• Consistent ID Generation: Modified BlazeCWorkspace to utilize BlazeResolveConfigurationID when adding new OCResolveConfiguration instances, ensuring consistent ID generation and usage.
• BlazeResolveConfiguration Enhancement: Added a getUniqueId() method to BlazeResolveConfiguration to return the newly defined BlazeResolveConfigurationID, improving its integration with the new ID system.

Using Gemini Code Assist

The full guide for Gemini Code Assist can be found on our documentation page, here are some quick tips.

Invoking Gemini

You can request assistance from Gemini at any point by creating a comment using either /gemini <command> or @gemini-code-assist <command>. Below is a summary of the supported commands on the current page.

Feature	Command	Description
Code Review	/gemini review	Performs a code review for the current pull request in its current state.
Pull Request Summary	/gemini summary	Provides a summary of the current pull request in its current state.
Comment	@gemini-code-assist	Responds in comments when explicitly tagged, both in pull request comments and review comments.
Help	/gemini help	Displays a list of available commands.

Customization

To customize Gemini Code Assist for GitHub experience, repository maintainers can create a configuration file and/or provide a custom code review style guide (such as PEP-8 for Python) by creating and adding files to a .gemini/ folder in the base of the repository. Detailed instructions can be found here.

Limitations & Feedback

Gemini Code Assist may make mistakes. Please leave feedback on any instances where its feedback is incorrect or counter productive. You can react with 👍 and 👎 on @gemini-code-assist comments. If you're interested in giving your feedback about your experience with Gemini Code Assist for GitHub and other Google products, sign up here.

Footnotes

1. Review the Privacy Notices, Generative AI Prohibited Use Policy, Terms of Service, and learn how to configure Gemini Code Assist in GitHub here. Gemini can make mistakes, so double check it and use code with caution. ↩

[gemini-code-assist]

Code Review

This pull request refactors how configuration IDs are handled by introducing a new BlazeResolveConfigurationID class to provide a more structured and unique identifier for resolve configurations. The BlazeConfigurationData.get method now directly accepts a configuration ID string, and BlazeCWorkspace uses the new BlazeResolveConfigurationID when adding configurations. A potential compilation error was noted in TransitionTest.java due to a method name mismatch (configurationId() vs configuration()), and the KDoc for the new BlazeResolveConfigurationID class is incomplete.