Remove old develop branch references after default branch renaming

[marcelovilla]

Reference Issues or PRs

Closes #2770

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?

You can manually trigger any of the cloud deployment workflows (i.e., AWS, Azure and Google Cloud) and specify main as the Nebari branch in the first text box (not from the dropdown menu in the first item).

Any other comments?

[Adam-D-Lewis]

They appear to be passing now. Is this PR still needed?

[viniciusdc]

I think the PR contents are still needed for legacy code removal, but the naming needs to be changed as well as the issue affiliation

[marcelovilla]

@Adam-D-Lewis huh, I thought this was the issue but you're right, they are passing now and pointing to the correct branch. As @viniciusdc mentioned, this PR is still relevant in the sense that it gets rid of old references to develop. I updated the issue title and opened and linked a new issue.