If an exact (eups tag) conda environment is used for lsstsw rebuild/publish, the resulting tag file published to eups.lsst.codes has the eups tag recorded rather than the underlying rubin-env version. This is unnecessary because the exact environment is recorded, and it makes lookup of the proper environment harder because those are stored by rubin-env version.

Change publish in lsstsw and run-publish in jenkins-dm-jobs to propagate the rubin-env version when available.