Local tests

[sei-vsarvepalli]

This pull request introduces several improvements to the CI/CD workflows and enhances the security and flexibility of the Harbor admin password setup. The most significant changes are the migration of CI jobs to a new runner, the implementation of a secure admin password prompt during installation, and the adjustment of configuration templates to support these changes.

CI/CD Infrastructure Updates:

• Migrated all CI workflow jobs in .github/workflows/CI.yml, .github/workflows/build-package.yml, .github/workflows/conformance_test.yml, and .github/workflows/publish_release.yml from the oracle-vm-24cpu-96gb-x86-64 runner to the ubuntu-24-large runner for improved reliability and maintainability. [1] [2] [3] [4] [5] [6] [7] [8] [9]

Admin Password Handling Improvements:

• Removed the default hardcoded admin password from make/harbor.yml.tmpl and replaced it with documentation and a commented-out example, encouraging users to set a secure password during installation. [1] [2]
• Added a password prompt and confirmation logic to make/install.sh, requiring users to set a non-empty, matching admin password interactively during installation if not provided via environment variable. The password is then securely written to harbor.yml. [1] [2]
• Updated tests/hostcfg.sh to append the admin password to harbor.yml if the HARBOR_ADMIN_PASSWD environment variable is set, supporting automated test setups.

Version Update:

• Bumped the application version from v2.15.0 to v2.16.0 in VERSION to reflect these changes.Thank you for contributing to Harbor!

Comprehensive Summary of your change

Issue being fixed

Fixes #(issue)

Please indicate you've done the following:

• Well Written Title and Summary of the PR
• Label the PR as needed. "release-note/ignore-for-release, release-note/new-feature, release-note/update, release-note/enhancement, release-note/community, release-note/breaking-change, release-note/docs, release-note/infra, release-note/deprecation"
• Accepted the DCO. Commits without the DCO will delay acceptance.
• Made sure tests are passing and test coverage is added if needed.
• Considered the docs impact and opened a new docs issue or PR with docs changes if needed in website repository.