fix general node scaling bug for azure

[Adam-D-Lewis]

Reference Issues or PRs

Fixes #2516

What does this implement/fix?

Put a x in the boxes that apply

• Bug fix (non-breaking change which fixes an issue)
• New feature (non-breaking change which adds a feature)
• Breaking change (fix or feature that would cause existing features not to work as expected)
• Documentation Update
• Code style update (formatting, renaming)
• Refactoring (no functional changes, no API changes)
• Build related changes
• Other (please describe):

Testing

• Did you test the pull request locally?
• Did you add new tests?

Any other comments?

[viniciusdc]

LGTM, thanks for catching it @Adam-D-Lewis

[viniciusdc]

Also, it's pretty interesting to discover that the order of our default node groups in our configuration matters.

[Adam-D-Lewis]

Also, it's pretty interesting to discover that the order of our default node groups in our configuration matters.

Oh yeah, I hope that's not the case. I hope we're making sure we pass in the general node group first to terraform at least regardless of it's order in nebari-config.yaml