Aks [nodepool] update without args prompts to reconcile.

[paulgmiller]

---

This is an alternateive to #4719 aks is debating.

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

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?

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 PR is merged into master branch, a new PR will be created to update src/index.json automatically.
The precondition is to put your code inside this repo and upgrade the version in the PR but do not modify src/index.json.

[yonzhan]

AKS

[matthchr]

minor: Use ' rather than " for consistency, since from what I can tell that's the style used elsewhere in this file.

[paulgmiller]

@FumingZhang I think we're good on the aks side so looking for your review at this point.

[FumingZhang]

LGTM

[FumingZhang]

In addition, the CI failure is due to a test case that is not related to this PR. Will fix it in another PR.

[zhoxing-ms]

Do you need to add a new version for this extension to release these changes? If so, please also modify the HISTORY.rst and setup.py files

[paulgmiller]

Do you need to add a new version for this extension to release these changes? If so, please also modify the HISTORY.rst and setup.py files

I'm not sure what the pattern is here do we bump the version on every change or batch several of them?

Bumped version and HISTORY.md but not actually what is normal here.

In addition, the CI failure is due to a test case that is not related to this PR. Will fix it in another PR.

Is there a way to rerun tests?

[zhoxing-ms]

I'm not sure what the pattern is here do we bump the version on every change or batch several of them?
Bumped version and HISTORY.md but not actually what is normal here.

@paulgmiller It mainly depends on whether you want these features to be released immediately in a new extension version?
Please note that if you do not upgrade the extension version, these codes will only be merged to extension repo, but will not be released for the time being