Test calvinshum dev

[AllyW]

---

This checklist is used to make sure that common guidelines for a pull request are followed.

Related command

General Guidelines

• Have you run azdev style <YOUR_EXT> locally? (pip install azdev required)
• Have you run python scripts/ci/test_index.py -q locally? (pip install wheel==0.30.0 required)
• My extension version conforms to the Extension version schema

For new extensions:

• My extension description/summary conforms to the Extension Summary Guidelines.

About Extension Publish

There is a pipeline to automatically build, upload and publish extension wheels.
Once your pull request is merged into main branch, a new pull request will be created to update src/index.json automatically.
You only need to update the version information in file setup.py and historical information in file HISTORY.rst in your PR but do not modify src/index.json.

[github-actions]

🔎
Please ensure to format the placeholder and URLs properly as per the guidelines:

+To release a new version, please select a new version number (usually plus 1 to last patch version, X.Y.Z -> Major.Minor.Patch, more details in `\doc <https://semver.org/>`_), and then add a new section named as the new version number in this file, the content should include the new modifications and everything from the *Pending* section. Finally, update the `VERSION` variable in `setup.py` with this new version number.

• Replace \doc <https://semver.org/>_ with appropriate surrounding HTML tags or use backticks for placeholders and ensure the URL link is marked as an example if not accessible.

[github-actions]

🔎
Consider using an enumeration to define the constants for better code organization and type safety.

from enum import Enum

class TlsManagement(Enum):
    MANAGED = "Managed"
    NONE = "None"

class GpuDriverType(Enum):
    CUDA = "CUDA"
    GRID = "GRID"

[github-actions]

🔎
--driver-type should use backticks for the placeholders "GRID" and "CUDA" to clearly denote them as specific values:

- short-summary: Specify the type of GPU driver to install when creating Windows agent pools. Valid values are "GRID" and "CUDA". 
+ short-summary: Specify the type of GPU driver to install when creating Windows agent pools. Valid values are `GRID` and `CUDA`. 

[github-actions]

🔎
Ensure the new parameter driver_type is documented and handled appropriately within the function. If driver_type needs validation or default values, add those. For example:

if driver_type is not None:
    # Validate driver_type options or set default if needed
    valid_driver_types = ['type1', 'type2']
    if driver_type not in valid_driver_types:
        raise ValueError(f"Invalid driver_type: {driver_type}. Must be one of {valid_driver_types}")

[github-actions]

🔎
PR Summary:

1. Added --driver-type parameter to the az aks nodepool add command.
2. Updated relevant test cases to include test_aks_gpu_driver_type.
3. Introduced constants for GPU driver types: CONST_GPU_DRIVER_TYPE_CUDA and CONST_GPU_DRIVER_TYPE_GRID.
4. Implemented logic to handle the --driver-type parameter within the AKS agent pool configuration.
5. Updated documentation to reflect the new --driver-type option.
6. Bumped the package version from 9.0.0b3 to 9.0.0b4.

[github-actions]

Hi @AllyW

⚠️ Release Requirements

Module: aks-preview

• ⚠️ Please update VERSION to be 13.0.0b7 in src/aks-preview/setup.py

Notes

• For more info about extension versioning, please refer to Extension version schema