no-jira: changed tenant.ui.profile.plugin build branch to develop;

[spirosdi]

What does this do?
It changes the tenant.ui.profile.plugin.build.branch build property to develop from main for all the profiles.

Why are we doing this? (with JIRA link)
Now the new ui profile plugin patch versions are getting released automatically. So for all the ui profile plugin repos, we need a ready-to-release main branch and a develop one for the development work. Similar to the cspace-ui. We also need to build the develop branch instead of the main branch when deploying with CSPACE_UI_BUILD env var set to true.

How should this be tested? Do these changes have associated tests?
Locally, please set the CSPACE_UI_BUILD env var to true. Then build and deploy. Confirm that the build is green and when opening the different http://localhost:8180/cspace/{profile}/welcome screens, the UI version commit is set to the one last pushed to the develop branch (for the botgarden, herbarium and bonsai the commit is the same in both main and develop branch). Please check all the profiles:

• anthro
• publicart
• materials
• lhmc
• fcart
• botgarden
• herbarium
• bonsai

Dependencies for merging? Releasing to production?
No dependencies

Has the application documentation been updated for these changes?
N/A

Did someone actually run this code to verify it works?
@spirosdi ran it locally

Have any new security vulnerabilities been handled?
N/A

[spirosdi]

@mikejritter , I will merge this PR now so that Jessi has a chance to check the home location before her time off. In any case, please do check the change when you have time.