missing CI to verify that EESSI-extend modules are in sync

While we have a CI workflow that checks that the EESSI-extend module is working as expected, we're not checking whether the modules deployed in `software.eessi.io` are in sync with the scripts that create them.

We should add an extra step to the existing `tests_eessi_extend_module.yml` workflow for this.