build(ci-cd): add bump version github workflow

[DaveXiong]

Description

Add a bump version github workflow, the workflow should be triggered manually and the following inputs required:

• branch
• new-version

The workflow will:

• create a new branch based on the branch
• set the new-version in pom.xml and package.json files
• create a PR to the branch

Related Issue

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)
• Refactoring or add test (improvements in base code or adds test coverage to functionality)
• CI/CD or documentation update (changes to CI/CD pipeline or documentation)

Checklist

• I ensured that the documentation is up to date
• I explained why this PR updates in detail with reasoning why it's required
• I would like a code coverage CI quality gate exception and have explained why

[github-actions]

Library Vulnerability scan results

The following vulnerabilities have been found in libraries included in the repository (some might be dependencies of dependencies).

Critical 🔴 and High 🟡 severity vulnerabilities must be fixed before the PR can be merged, even if they are dependencies of dependencies.

Library	Vulnerable version	Severity	Fix version	Vulnerability ID

[github-actions]

Library Vulnerability scan results

The following vulnerabilities have been found in libraries included in the repository (some might be dependencies of dependencies).

Critical 🔴 and High 🟡 severity vulnerabilities must be fixed before the PR can be merged, even if they are dependencies of dependencies.

Library	Vulnerable version	Severity	Fix version	Vulnerability ID

[github-actions]

Library Vulnerability scan results

The following vulnerabilities have been found in libraries included in the repository (some might be dependencies of dependencies).

Critical 🔴 and High 🟡 severity vulnerabilities must be fixed before the PR can be merged, even if they are dependencies of dependencies.

Library	Vulnerable version	Severity	Fix version	Vulnerability ID

[github-actions]

Library Vulnerability scan results

The following vulnerabilities have been found in libraries included in the repository (some might be dependencies of dependencies).

Critical 🔴 and High 🟡 severity vulnerabilities must be fixed before the PR can be merged, even if they are dependencies of dependencies.

Library	Vulnerable version	Severity	Fix version	Vulnerability ID

[github-actions]

Library Vulnerability scan results

The following vulnerabilities have been found in libraries included in the repository (some might be dependencies of dependencies).

Critical 🔴 and High 🟡 severity vulnerabilities must be fixed before the PR can be merged, even if they are dependencies of dependencies.

Library	Vulnerable version	Severity	Fix version	Vulnerability ID

[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 SonarCloud