Deploy to staging server

[eloiferrer]

Issue description: We need a staging environment to deploy changes before publishing them in production.

• Changes in the 'main' branch will be automatically deployed to mardi03 (staging)
• Tags will be used in portal-compose to deploy specific tagged versions to mardi02 (production)

TODOS:

• [ ] example todo to copy

Acceptance-Criteria

Checklist for this issue:

• [ ] Assignee has been set for this issue
• [ ] All fields of the issue have been filled
• [ ] Issue has been assigned to the main project
• [ ] Code was merged
• [ ] Feature branch has been deleted and issues were updated / closed
• [ ] Issue is tracked by an epic, or the label 'non-epic' is set to the issue.

[eloiferrer]

staging.mardi4nfdi.org and *.staging.mardi4nfdi.org point now to mardi03

[eloiferrer]

• docker-compose.yml has been rewritten to list all pulled images at the top of the document (https://github.com/MaRDI4NFDI/portal-compose/pull/465)
• docker-compose.yml file has been split in docker-compose.yml and docker-compose-extra.yml (https://github.com/MaRDI4NFDI/portal-compose/pull/465)
• mardi02 and mardi03 deploy scripts have been updated to deploy both docker-compose & docker-compose-extra.

[eloiferrer]

• Tag v1.0 has been added to main branch in portal-compose
• mardi03 deploys main branch
• mardi02 deploys main branch at tag v1.0

[eloiferrer]

• Documentation for deployment has been updated: https://github.com/MaRDI4NFDI/portal-compose?tab=readme-ov-file#deploy-on-the-mardi-server
• mardi03 uses the main branch
• mardi02 deploys the specified tagged version in the deploy script in mardi02