Readme and auto table update workflow

[e-perl-NOAA]

What is the feature?

• Update the Readme with better info about the repo and added a workflow to auto update the table

How have you implemented the solution?

• The workflow uses info in the yml of each qmd (except like the template and a few others) to fill in some of the table and then runs each qmd separately, and creates a badge if it passes or fails, pushes only the successfully rendered files to the github.io site IF it is a push or a merged pr on main, creates a PR with the updated readme file badges

Disclaimer: I doubt this PR is ready yet, I just wanted to go ahead and make it so the work being done here is more visible

[e-perl-NOAA]

@kellijohnson-NOAA, I made some more changes. This should be able to replace the current render-and-publish.yml which I have deleted in this PR as well. What I hate about github actions is that, I'm always like ... well ... you can't see it here but I tested it and it worked then, let's 🫰and 🙏🏻 that it still works when it gets merged in to main 😬😆

[iantaylor-NOAA]

@e-perl-NOAA and @kellijohnson-NOAA, I just looked through this PR and I like it.

Having a clear message when one of the case studies breaks will be really helpful. There will be a bit of additional work when adding or modifying an existing case study, but that shouldn't be too hard to deal with and the patterns for all the others should make it clear what to add and change.

I'm not great with .yml, but I ran the R script within the workflow locally. I had to remove the "🧪🛏️" which caused an incomplete reading of the README file, but after that it was successfully updated by the script.

[iantaylor-NOAA]

A trivial suggestion I forgot to make earlier.
I would replace the use of sprintf() with glue::glue() (copilot has done that for me several times when I've asked), which I think improves readability of the code.

[kellijohnson-NOAA]

Just a few suggestions but feel free to merge this in whenever you are ready.