Use tofu binary instead of terraform one

[marcelovilla]

Reference Issues or PRs

Closes #2762

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?

How to test this PR?

I think there are two important things to test with this PR: (1) deploy from scratch using the OpenTofu binary, and (2) upgrade an existing cluster using the OpenTofu binary. To test:

1. Deploy Nebari off of this branch, either locally or to any of the supported cloud providers.
2. Upgrade an existing Nebari deployment using this branch and redeploy

All resources should be correctly deployed and Nebari should be running as usual after.

Any other comments?

This has been successfully tested in the following scenarios:

• Local deployment
• AWS deployment
• GCP deployment
• Upgrade of existing 2024.9.1 GCP deployment to 8f709da

[Adam-D-Lewis]

Have you tested an upgrade? I think we should test one on an existing deployment just to be sure no issues will arise.

[marcelovilla]

Have you tested an upgrade? I think we should test one on an existing deployment just to be sure no issues will arise.

@Adam-D-Lewis I did test an upgrade on GCP and everything went smooth. I still think it would be worthwhile to test both an AWS and Azure upgrade

[marcelovilla]

Here's a passing local upgrade test: https://github.com/nebari-dev/nebari/actions/runs/11740475035/job/32707098771

[dcmcand]

Tested locally with clean install and upgrade from 2024.7.1. Does what it says on the tin. 🚀