Update publish-conda to use the new tag for the package version

[ceblanton]

Describe your changes

Run the publish-conda action on pushes to main or after the update-tag action has run.

We detect the latter case by a closed pull request on a main push AND the if-condition that checks that the source branch is the one triggered by the update-tag reference changes.

The "Set version for tagged release" is needed to inform conda-build of the tag. Because there are intermediate commits (the updated version refs) the commit no longer is tagged. So we can retrieve the package version from init.py

Issue ticket number and link (if applicable)

Fixes #921

Checklist before requesting a review

• I ran my code
• I tried to make my code readable
• I tried to comment my code
• I wrote a new test, if applicable
• I wrote new instructions/documentation, if applicable
• I ran pytest and inspected it's output
• I ran pylint and attempted to implement some of it's feedback
• No print statements; all user-facing info uses logging module

Note: If you are a code maintainer updating the tag or releasing a new fre-cli version, please use the release_procedure.md template. To quickly use this template, open a new pull request, choose your branch, and add ?template=release_procedure.md to the end of the url.

[codecov]

Codecov Report

✅ All modified and coverable lines are covered by tests.
✅ Project coverage is 82.09%. Comparing base (6388696) to head (06518dc).

Additional details and impacted files

@@           Coverage Diff           @@
##             main     #922   +/-   ##
=======================================
  Coverage   82.09%   82.09%           
=======================================
  Files          67       67           
  Lines        3736     3736           
=======================================
  Hits         3067     3067           
  Misses        669      669           

Flag	Coverage Δ
unittests	82.09% <ø> (ø)

Flags with carried forward coverage won't be shown. Click here to find out more.

---

Continue to review full report in Codecov by Harness.

Legend - Click here to learn more
Δ = absolute <relative> (impact), ø = not affected, ? = missing data
Powered by Codecov. Last update 6388696...06518dc. Read the comment docs.

🚀 New features to boost your workflow:

• ❄️ Test Analytics: Detect flaky tests, report on failures, and find test suite problems.