Upgrade to Pydantic V2 [Wait til after 2024.4.1 release to merge]

[Adam-D-Lewis]

Reference Issues or PRs

This is a continuation of @fangchenli's work - #1928
Fixes #2343

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): Upgrade dependencies

Testing

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

Any other comments?

[Adam-D-Lewis]

Looks like the Local Integration Tests started failing when I merged in develop branch, which was only updating the azurerm provider version, which passed tests on its PR. Not sure why it's failing now. I also deployed this locally, and it seems to be running fine.

Update: I see that the test uses the "main" image tags so the error is probably due to a recent change in nebari-docker-images repo.

Update2: Fixed now

[marcelovilla]

@Adam-D-Lewis I am seeing the same behavior in #2375. Did the Cypress tests succeed when running them locally?

Look at this screenshot from the failing test:

[marcelovilla]

🚀

[Adam-D-Lewis]

We are waiting to merge until after 2024.4.1 release to merge to give certain developers of Nebari extensions a chance to test them before we merge.

[marcelovilla]

We are waiting to merge until April 12 to give certain developers of Nebari extensions a chance to test them before we merge.

@Adam-D-Lewis should we add a [DO NOT MERGE] to the title just in case?

[marcelovilla]

@Adam-D-Lewis should we test whether upgrading from the last stable version to this does not result in any potential changes (e.g., terraform infrastructure being forced to be replaced or the render command not working properly or as expected)? I don't think that's going to be the case but it might be worth to take a look at. I can help with that if necessary.

C.C.: @viniciusdc

[Adam-D-Lewis]

Yes, it'd be good to test the upgrade.

[Adam-D-Lewis]

As an update, I tested the upgrade from 2024.3.3 on a local deployment and everything went smoothly. No infrastructure was replaced, etc.