Change docker tag to match version, not hardcoded

[marrts]

The current {DISTRO}-master dockers are pointing to tesseract_planning {OS}-0.21. This means they don't have the latest changes in tesseract or tesseract_planning. This change makes tesseract_ros2 consistent with tesseract_planning as seen here: https://github.com/tesseract-robotics/tesseract_planning/blob/f22b04dcbe14afe425c63d8bfbb4d14ee4255bcf/.github/workflows/docker.yml#L60

[marrts]

Working through some other issues at the moment to get this ready. tesseract-robotics/tesseract_qt#103

[marip8]

steps.meta.outputs.version is version information that is specific to this repository, not the parent image for which TAG is being specified. I think this needs to remain hard-coded to the specific version of the parent image that you want to pull.

[marrts]

Aren't version tags supposed to track across all repos of tesseract?

[marip8]

Yes for convenience they are all currently the same, but they don't technically have to be so this could break down in the future (and is already breaking down because the branch names are not all the same for all tesseract repos)

[marrts]

Aren't version tags supposed to track across all repos of tesseract?

This is not accurate because I see at least TrajOpt follows a different version number and that is what tesseract_planning builds off of.

So would you be okay with something like:

if PR -> reference master/main
if new main/master branch -> reference master/main
if tag -> reference {hard coded tag}

I feel like that most closely aligns with how tesseract PRs have been managed with regards to unstable/stable versions of CI.

@Levi-Armstrong, any input on this?

[Levi-Armstrong]

I think they should have the same major and minor version across all tesseract repositories and trajopt.

[marrts]

tesseract_qt was updated to use master instead of main and trajopt is set to match tesseract tags now per: tesseract-robotics/trajopt#397. For these reasons we should be able to proceed with this change.