[LoginNodes] Update API to support multiple login node pools

[cjmakin]

Description of changes

This change modifies the server and client API models and controllers to return list of pool statuses in the loginNodes section of describe-cluster. The login node pool name was also added to each pool status.

In addition, this change adds the pool name to describe-cluster-instances output.

• Updated smithy models to generate python server models.
• Copied changes from generated models to /cli/src/pcluster/api/models.
• Updated client models
• Updated cluster_operations_controller so that the login_nodes field of describe-cluster response contains a list of PoolStatus.
• Updated cluster_instances_controller to include login node pool name.
• Added pool_name property to InstanceInfo in aws_resources.

Example describe-cluster:

  "clusterName": "mult-pools-1",
    .
    .
    .
  "clusterStatus": "CREATE_COMPLETE",
  "scheduler": {
    "type": "slurm"
  },
  "loginNodes": [
    {
      "status": "active",
      "poolName": "pool1",
      "address": "mult-p-multp-eMr9BYRKZVDa-e5bb34f40b24f51d.elb.us-east-2.amazonaws.com",
      "scheme": "internet-facing",
      "healthyNodes": 1,
      "unhealthyNodes": 0
    },
    {
      "status": "active",
      "poolName": "pool2",
      "address": "mult-p-multp-PaQ7GgC27sic-aba10c890247b36b.elb.us-east-2.amazonaws.com",
      "scheme": "internet-facing",
      "healthyNodes": 1,
      "unhealthyNodes": 0
    }
  ]
}

Example describe-cluster-instances:

"instances": [
    {
      "launchTime": "2024-08-13T13:17:28.000Z",
      "instanceId": "i-0df02e911cc19b534",
      "poolName": "pool1",
      "publicIpAddress": "3.148.106.168",
      "instanceType": "t2.small",
      "state": "running",
      "nodeType": "LoginNode",
      "privateIpAddress": "10.0.0.196"
    },
]

Tests

• Manually tested modified commands
• Updated test_cluster_operations_controller.py unit test
• Updated and ran test_cli_commands integration test

References

• Link to impacted open issues.
• Link to related PRs in other packages (i.e. cookbook, node).
• Link to documentation useful to understand the changes.

Checklist

• Make sure you are pointing to the right branch.
• If you're creating a patch for a branch other than develop add the branch name as prefix in the PR title (e.g. [release-3.6]).
• Check all commits' messages are clear, describing what and why vs how.
• Make sure to have added unit tests or integration tests to cover the new/modified code.
• Check if documentation is impacted by this change.

Please review the guidelines for contributing and Pull Request Instructions.

By submitting this pull request, I confirm that my contribution is made under the terms of the Apache 2.0 license.

[hgreebe]

How come we are not doing these checks anymore?

[cjmakin]

I moved this portion to this function, and changed it to mock the function return values of specific objects. That way we can test different values for pool1 and pool2 in the response content