Renaming this repo to ufs-coastal-model

[janahaddad]

In an effort to bring more clarity and matching the structure of other UFS applications, let's keep discussing the idea of renaming this repo to ufs-coastal-model.

The idea is that ufs-coastal-app could bring (as it currently does in a limited way) ufs-coastal-model in as a submodule. I'm guessing that the way this is done depends on whether ufs-coastal-model fork of ufs-weather-model is eventually merged, or if we keep ufs-coastal-model separate from ufs-weather-model.

Here are some notes from emails/conversations we've had about this:

Things we'll need to check/mitigate if we change the name:

• the NOAA dev team’s clones across platforms need to be renamed, although git should dynamically correct
• collaborator’s clones need to be renamed especially if they plan on pushing to ufs-coastal: model component devs (eg VIMS folks), UFS-CAT testers
• anywhere in the main code base itself where the repo is named (bash scripts etc)
• anywhere in the model component forked repos/code?
• check application level scripts
• change path in build level
• documentation, all presentations, etc.

Couple resources on potential impacts of renaming a repo:

https://confluence.atlassian.com/bbkb/consequences-and-considerations-of-renaming-a-repository-1252333745.html#:~:text=Change%20in%20Repository%20URL%3A%20When,tracking%2C%20will%20have%20new%20addresses.
https://stackoverflow.com/questions/69839125/which-are-the-side-effects-of-renaming-a-git-repository

cc @uturuncoglu @pvelissariou1 @saeed-moghimi-noaa

[janahaddad]

Closing discussion with #71