Beta and TestFlight builds use one tag Github deployment

[pyby]

Motivation and Context

Thanks to #447, and beta update #454, tag deployments are implemented.
We can now follow the production rules: no multiple tag deployments on Beta and TestFlight builds as well.
Just update the current tag deployment if exist and not succeeded. Ignore running for just update distribution.

Description

• Check if tag deployment exist for Beta and AppStore builds. Update the deployment states if no already succeed.
• If the tag deployment exist and already succeed, do not create a new deployment.

Checklist

• The branch should be rebased onto the develop branch for whole tests with nighties, but it's not required.*
• The code followed the code style as make quality passes with a green tick on the last commit.
• Remote configuration properties have been properly documented (if relevant).
• The documentation has been updated (if relevant).
• Issues are linked to the PR, if any.

* The project uses Github merge queue feature, which rebases onto the develop branch before squashing and merging the PR.

[pyby]

Not working as expected when tested "AppstoreBuilds" for public TestFlight builds. Not started with a tag deployment, either a branch name deployment, but still with a commit sha. Needs more investigation.