Updating to common GitHub Action 1.0.5

[nikhil2611]

This pull request updates the CI workflow configuration to enable additional security scanning and improve language specification for analysis. The most significant changes are related to enabling BlackDuck Polaris scans and clarifying the language used for build and analysis.

Description

This pull request updates the CI workflow configuration in .github/workflows/ci-main-pull-request-stub.yml to improve security scanning and ensure correct build settings. The most important changes are:

Security and scanning improvements:

• Enabled BlackDuck Polaris SAST and SCA scans by setting perform-blackduck-polaris to true to ensure security checks are performed during CI runs.

Build and analysis settings:

• Set the language parameter to 'ruby' to specify the project's primary language for build and SonarQube analysis.
• Updated the STUB_VERSION environment variable from "1.0.4" to "1.0.5" to reflect the latest stub version.

Types of changes

• 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 change)
• Chore (non-breaking change that does not add functionality or fix an issue)

Checklist:

• I have read the CONTRIBUTING document.
• I have run the pre-merge tests locally and they pass.
• I have updated the documentation accordingly.
• I have added tests to cover my changes.
• If Gemfile.lock has changed, I have used --conservative to do it and included the full output in the Description above.
• All new and existing tests passed.
• All commits have been signed-off for the Developer Certificate of Origin.

[sonarqubecloud]

Quality Gate passed

Issues
0 New issues
0 Accepted issues

Measures
0 Security Hotspots
0.0% Coverage on New Code
0.0% Duplication on New Code

See analysis details on SonarQube Cloud

[jaymzh]

@nikhil2611 - updated tests are failing.

[nikhil2611]

@nikhil2611 - updated tests are failing.

@jaymzh Yeah its failing with FAILURE_ACCURACY_NOT_MET and we are trying to fix that.