split and modify mmg conda YAML

[chemiskyy]

No description provided.

[kmarchais]

I understand that the previous single file was not ideal but I am wondering if it doesn't impact the maintainability to have four different files for this.

Maybe we could refactor the single file to be more maintainable?
Here is an example generated by a LLM.

name: Create conda package for mmg

on:
  workflow_dispatch:

jobs:
  build_and_upload:
    name: Build on ${{ matrix.os }} (${{ matrix.conda_platform }})
    runs-on: ${{ matrix.os }}
    strategy:
      fail-fast: false
      matrix:
        include:
          - os: ubuntu-latest
            conda_platform: linux-64
          - os: macos-13
            conda_platform: osx-64
          - os: macos-latest
            conda_platform: osx-arm64
          - os: windows-latest
            conda_platform: win-64

    steps:
      - name: Checkout repository
        uses: actions/checkout@v4

      - name: Setup Miniconda
        uses: conda-incubator/setup-miniconda@v3
        with:
          miniconda-version: "latest"
          activate-environment: packaging

      - name: Install dependencies and login to Anaconda
        run: |
          conda install python=3.9 conda-build anaconda-client --yes --quiet
          anaconda logout
          anaconda login --username ${{ secrets.ANACONDA_USERNAME }} --password ${{ secrets.ANACONDA_PASSWORD }}

      - name: Build conda package
        run: |
          conda-build mmg.recipe -c conda-forge -c set3mah --output-folder .

      - name: Upload conda package
        run: |
          anaconda upload ${{ matrix.conda_platform }}/*.tar.bz2 --force

[chemiskyy]

You are right we can generate a matrix, I will update the file accordingly

[kmarchais]

LGTM, I updated the version of actions/checkout to v6.