Expand README to tell how to put it all together with emphasis on module testing

[tbrowder]

iThe github description of workflows is terrible. The bones of a useful workflow are here, but a bit more detail is needed for those of us who aren't very sure how it all fits together and works for our own module testing. For example:

1. Does the name of the *.yml (or *.yaml) file have any significance?
2. Where is the source of the actions/checkout version?
3. Where is the source of the Raku/actions version?
4. Where can I read about the format of a yaml file?
5. How can I test my mytest.yml file?

I would like to see a couple of examples that are useful in specific instances such as having to add extra packages or compiling and executing a user library.

I would also like to see workflows discussed in the docs for module publishers.

I have started a new Raku repository (github-workflow-examples) for such examples.

[skaji]

I have started a new Raku repository (github-workflow-examples) for such examples.

Sounds good.