GH actions for top level #2

That triggers the actions in subdirs.

As of today, GH workflows can only live in the top-level .github/workflows directory. They cannot live in subdirectories. Thus there is no way to use a top-level workflow to trigger workflows in subdirectories (because they are not allowed to live there).

Instead:

I renamed the per-project workflows.
I set the working-directory within each (to cause the action to be executed using the appropriate subdirectory as working directory), and
I moved them into the top-level .github/workflows directory.

The workflows can probably be simplified further (e.g., consolidated into fewer). For now, however, we are 🤘

As of today, GH workflows can only live in the top-level `.github/workflows` directory. They cannot live in subdirectories. Thus there is no way to use a top-level workflow to trigger workflows in subdirectories (because they are not allowed to live there). Instead: 1. I renamed the per-project workflows. 1. I set the `working-directory` within each (to cause the action to be executed using the appropriate subdirectory as working directory), and 1. I moved them into the top-level `.github/workflows` directory. The workflows can probably be simplified further (e.g., consolidated into fewer). For now, however, we are 🤘

Labels Milestones

GH actions for top level #2