Merge main branch into develop branch to synchronize branches

[JRocabruna]

Description

This pull request merges the main branch into the develop branch to synchronize the two branches and ensure that develop is up-to-date with the latest changes from main. This step is essential to maintain consistency and resolve any discrepancies between the branches.

• Related Issue: N/A
• Type of Change:
  • New feature (non-breaking change which adds functionality)

Checklist

Please ensure the following guidelines are met:

• The code follows the style guidelines of this project.
• A self-review has been performed on the code.
• The code is well-documented, and comments have been added where necessary.
• Tests have been added to prove that the fix is effective or that the feature works. All existing tests pass.
• Commit messages follow the convention type(scope): description.
• The pull request has no conflicts with the base branch.
• Any dependent changes have been merged and published in downstream modules.

Additional Information

This is a routine update to ensure that the develop branch reflects the latest changes from main. No additional features or bug fixes are introduced in this pull request.

[github-advanced-security]

This pull request sets up GitHub code scanning for this repository. Once the scans have completed and the checks have passed, the analysis results for this pull request branch will appear on this overview. Once you merge this pull request, the 'Security' tab will show more code scanning analysis results (for example, for the default branch). Depending on your configuration and choice of analysis tool, future pull requests will be annotated with code scanning analysis results. For more information about GitHub code scanning, check out the documentation.

[DarkRockMountain-admin]

Comments

This is a well-structured update to the Release Drafter configuration. The addition of categories enhances the automation process and aligns with contribution guidelines.

Review Checklist

• Code adheres to the project's coding guidelines.
• Changes are well-documented.
• Tests have been added/updated and pass successfully.
• Commit messages follow the correct format: type(scope): description.
• No conflicts with the base branch.

Approval

Approved: Changes look good and meet the project's contribution standards.