[Improvement] Run static fleet checks only if there are static nodes

[himani2411]

Description of changes

• Add TOTAL_MIN_COUNT of a cluster as comment in /opt/slurm/etc/slurm_parallelcluster.conf which is later read to check if we have Static nodes or not.
• Run static fleet checks if there are any static nodes and run Protected Mode checks irrespective of node type

Tests

• Manual test for updating /opt/slurm/etc/slurm_parallelcluster.conf

test-suites:
  update:
    test_update.py::test_dynamic_file_systems_update:
      dimensions:
      - instances:
        - c5.xlarge
        oss:
        - alinux2023
        regions:
        - eu-west-2
        schedulers:
        - slurm
    test_update.py::test_dynamic_file_systems_update_data_loss:
      dimensions:
      - instances:
        - c5.xlarge
        oss:
        - rhel9
        regions:
        - eu-west-2
        schedulers:
        - slurm
    test_update.py::test_dynamic_file_systems_update_rollback:
      dimensions:
      - instances:
        - c5.xlarge
        oss:
        - rocky9
        regions:
        - rocky9
        schedulers:
        - slurm
    test_update.py::test_login_nodes_update:
      dimensions:
      - instances:
        - c5.xlarge
        oss:
        - rhel8
        regions:
        - us-east-2
        schedulers:
        - slurm
    test_update.py::test_multi_az_create_and_update:
      dimensions:
      - instances:
        - c5.xlarge
        oss:
        - alinux2
        regions:
        - eu-west-2
        schedulers:
        - slurm
    test_update.py::test_update_slurm:
      dimensions:
      - instances:
        - c5.xlarge
        oss:
        - rhel8
        regions:
        - eu-central-1

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.

[gmarciani]

The functionality is based on the presence of a comment in a config file.
This is a fragile approach since comments are meant to be removable without any side effect.

Why not getting the total number of static nodes from the cluster config file instead?

[himani2411]

That was the initial idea, however I wanted to see if we do loop through the cluster-config specifically for Scheduling section and this file is where we do it.

Even if somebody removes the comment it has to be at a point when the HeadNode is created and even if they remove this comment we can still go ahead and assume that the nos of static node is 1 and continue the old path.