New govpp tagging.

[VitalyGushin]

#18

[glazychev-art]

I'm not sure that we need to use a separate Release workflow file. Because govpp is not a typical cmd-* repository. It has a special way of building.
Main differences:

• we are running a special powerful server to build this image. (see name: Setup actions runner from ci.yaml). Simple github servers cannot do this.
• Docker image build uses certain flags (--target vpp).
• we don't need to update deployments-k8s because deployments-k8s doesn't use govpp directly. Instead we update cmd-* repositories (see update-dependent-repositories.yaml).

I would suggest modifying ci.yaml and update-dependent-repositories.yaml to make a release.

[glazychev-art]

I still think we need changes in update-dependent-repositories.yaml
For example:

govpp/.github/workflows/update-dependent-repositories.yaml

Line 71 in 3c0a753

go get -u github.com/${{ github.repository }}@${{ github.sha }}

=>
go get -u github.com/${{ github.repository }}@${{ inputs.docker_tag }}

or cosmetic

govpp/.github/workflows/update-dependent-repositories.yaml

Line 45 in 3c0a753

echo "Update go.mod and go.sum to latest version from ${{ github.repository }}@main" >> /tmp/commit-message

=>
...from ${{ github.repository }}@${{ inputs.docker_tag }}
What do you think?

[VitalyGushin]

@glazychev-art I think the behaviour won't change essentially, but it might be more informative. Fixed.