Experiment with a setup-dune based more-ci workflow

[mbarbin]

No description provided.

[coveralls]

Pull Request Test Coverage Report for Build 34

Details

• 0 of 0 changed or added relevant lines in 0 files are covered.
• No unchanged relevant lines lost coverage.
• Overall coverage remained the same at 100.0%

---

Totals
Change from base Build 33:	0.0%
Covered Lines:	245
Relevant Lines:	245

---

💛 - Coveralls

[mbarbin]

This is a follow-up to mbarbin/catch-the-bunny#20 where here we have one dune-workspace file per ocaml-version to be tested.

This almost works, except the -dev package cannot be resolved with ocaml 4.14 thus the setup-dune step fails during constraint resolution on the dune-pkg-more-ci workflow.

I think we could make this work if setup-dune accepted an additional only-packages: input, and then here we'd do:

       - name: Setup Dune
         uses: mbarbin/setup-dune@fd640f52b2a84d68cd4867cb5972247b70630d1a # repkg
         with:
           workspace: ${{ env.DUNE_WORKSPACE }}
+          only-packages: print-table,print-table-tests
           steps: install-dune enable-pkg lazy-update-depexts install-gpatch install-depexts

cc @shym for potential upstream setup-dune discussion