better workflow for adding new ghactions

[k-doering-NOAA]

Thanks @Bai-Li-NOAA for identifying this.

On #121 @Bai-Li-NOAA noted that the tests fail initially before merging into main, which is expected. Perhaps we should change how our tests work so that they aren't expected to fail when new reusable workflows are added.

I assume the failed checks on the pull request will run successfully after merging the changes into the main branch. I wonder if the errors from local checks can be resolved by writing custom expectations (e.g., expect_proj_file()). I've seen some examples in the {usethis} tests, but the utility functions for the active project seem very complicated.

[k-doering-NOAA]

We should explore if there is a path forward on this, or if dealing with the limitations of the current workflow is acceptable.