Update master with changes from v2.0

[tzanio]

No description provided.

[tzanio]

@pazner and @v-dobrev, I forgot about this PR... should we merge it?

[pazner]

Yes, I think so. I don't see any issues with it…

[adrienbernede]

@tzanio @pazner @v-dobrev Let me just explain why master was behind v2.0

Repos use mfem/github-actions by pointing to a specific ref.

My beginner mistake was to have mfem initially point at mfem/github-actions@master.
The mistake became obvious when I had to change mfem CI on both mfem and mfem/github-acitons side with a change of the interface between the two: those working with an "older" MFEM would have failures in the CI.

This is why I now use numbered versions (v1.0, v2.0): each time I need to change the interface, I increase the version major, otherwise we most likely want to merge in the vX.0 branch so that all the users immediately benefit from this.

In the end, master was behind because it corresponded to the first "numbered version", a sort of v0.0. I couldn’t update it without risking to break the CI for some branches.

You did well merging everything to master as long as you are aware of the above caveat. Most like, little to now branch were impacted because they had enough time to update.