feat(aes-action): [CLIENT-4213] adding initial changes to add aes action for workflows

[mirzakaracic]

No description provided.

[mirzakaracic]

PR's to refactor/remove built in run-ee-server with setup-aes shared action.

https://github.com/aerospike/aerospike-client-java-fluent/pull/13
aerospike/aerospike-client-java#553

[Copilot]

Pull request overview

This PR introduces a new GitHub Action for setting up Aerospike Enterprise Server (AES) containers in CI/CD workflows. The action supports single-node and multi-node cluster deployments with optional TLS encryption, custom configuration files, and environment variable passthrough.

Changes:

• Added setup-aes composite action with support for multi-node clustering, TLS, and custom configurations
• Added comprehensive test workflow covering single-node, multi-node, TLS, features, and environment variables scenarios
• Added wait-for-aes.sh script implementing three-phase readiness checks (node ready, cluster formation, migrations complete)

Reviewed changes

Copilot reviewed 4 out of 4 changed files in this pull request and generated 7 comments.

File	Description
.github/workflows/test_setup-aes.yaml	Test workflow with 5 jobs testing various action configurations and verifying outputs
.github/actions/setup-aes/action.yaml	Main composite action implementing JFrog authentication, TLS cert generation, Docker container orchestration, and config management
.github/actions/setup-aes/wait-for-aes.sh	Bash script with robust error handling for waiting on container readiness and cluster formation
.github/actions/setup-aes/README.md	Documentation with prerequisites, quick start examples, input/output reference, and usage notes

---

💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.

[arrowplum]

Some small changes but naming and defaults are important.

[arrowplum]

as discussed we will rename to setup aerospike or setup aerospike-server