Update pr.yml to publish collections to production upon PR merge

[botanical]

Context

In pr.yml, we currently have a no-op to publish collections to production. Update this step so that the collection is published to production when the PR is merged.

veda-data/.github/workflows/pr.yml

Lines 233 to 241 in 57f1005

	publish-to-prod-on-pr-merge:
	if: ${{ github.event_name == 'pull_request' && github.event.action == 'closed' && github.event.pull_request.merged == true }}
	runs-on: ubuntu-latest
	steps:
	- name: Checkout code
	uses: actions/checkout@v3
	- name: Publish to production on PR merge
	run: echo "NO-OP. This step runs when a PR is merged."

The dataset DAG now has an optional transfer option which transfers the assets to the production bucket and then starts discovery and ingest: NASA-IMPACT/veda-data-airflow#259.

Acceptance Criteria

• no-op step is removed and replaced with a step that transfers assets and then publishes the collection to production when the PR is merged
• relevant testing is done to ensure step works correctly

[smohiudd]

blocked by NASA-IMPACT/veda-data-airflow#256