Merge

[nodoubtz]

This pull request introduces multiple new GitHub Actions workflows to automate various tasks, including code scanning, dependency review, container deployment, and package publishing. The changes are organized by workflow theme, focusing on code quality, dependency management, container deployment, and package publishing.

Code Quality and Security:

• .github/workflows/5codeql.yml: Added a CodeQL workflow to analyze repository code for vulnerabilities, supporting multiple languages and providing options for custom queries and build logic.
• .github/workflows/dependency-review.yml: Added a Dependency Review workflow to scan dependency manifest files in pull requests for known vulnerabilities, with optional PR comment summaries.

Container Deployment:

• .github/workflows/google.yml: Added a workflow to build, publish, and deploy Docker containers to Google Kubernetes Engine (GKE), with configurations for Google Cloud APIs and Workload Identity Federation.
• .github/workflows/ibm.yml: Added a workflow to build, publish, and deploy Docker containers to IBM Kubernetes Service (IKS), including IBM Cloud CLI setup and authentication.

Package Publishing:

• .github/workflows/npm-publish-github-packages.yml: Added a workflow to test and publish Node.js packages to GitHub Packages upon release creation.
• .github/workflows/npm-publish.yml: Added a workflow to test and publish Node.js packages to npm registry upon release creation.

Other Workflows:

• .github/workflows/manual.yml: Added a manually triggered workflow for custom tasks, accepting user inputs via the Actions UI.
• .github/workflows/static.yml: Added a workflow to deploy static content to GitHub Pages, ensuring concurrency control for deployments.
• .github/workflows/npm-grunt.yml: Added a Node.js workflow with Grunt for builds, supporting multiple Node.js versions and caching node_modules.

Minor Update:

• .github/workflows/release-new-action-version.yml: Updated the TAG_NAME input default value for the release workflow to 'Lit2dafit'.

Description

Motivation and Context

How Has This Been Tested?

Screenshots (if appropriate):

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)
• [ ] Documentation (add or update README or docs)

Checklist:

• [ ] My code follows the code style of this project.
• [ ] My change requires a change to the documentation.
• [ ] I have updated the documentation accordingly.
• [ ] I have read the CONTRIBUTING document.
• [ ] I have added tests to cover my changes.
• [ ] All new and existing tests passed.