Node pool name customisation

[melzayet]

PR Summary

User node pool name should be customisable

PR Checklist

• PR has a meaningful title
• Summarized changes
• This PR is ready to merge and is not Work in Progress
• Link to a filed issue:
• Screenshot of UI changes (if PR includes UI changes)

As described in issue #461, user node pool is made configurable

In case of only system node pools, the parameter is not set.

If no value provided by user, it defaults to npuser01, the original string that was used

[Gordonby]

Logic looks good.
I'll fire up a couple of tests then we can merge. Great PR 😀

[melzayet]

@Gordonby one thing I am was not sure of is whether the text input field should be required (with the red asterik).

It's required unless only system node pool exists. It's currently always required. What's your thoughts?

[Gordonby]

I actually think we can lean into the system pool a little more. It might make the required bit a little easier.

In the scenario of just a system pool being deployed;

• We relabel the textbox to "Node Pool Name"
• We allow the system pool to also be renamed
  

Thoughts?

[Gordonby]

Can we add an output of the pool name(s) ?
This way if a consuming bicep/pipeline uses AKSC then it'll be easy to grab the poolnames.

[melzayet]

@Gordonby suggestions absolutely make sense. I have implemented, tested and committed those.

I just want to highlight the commenting out of code block startling line 50 in clusterTab.js. This was clearing vmSKU without any changes in compute type