Enable custom release command in aicoe-ci

[vpavlin]

Is your feature request related to a problem? Please describe.
Currently aicoe-ci simply uses git branch & git tag to produce a release. In some cases (e.g. odh-manifests) there are additional steps needed to produce the release successfully.

Describe the solution you'd like
It would be ideal if aicoe-ci allowed to specify a release command with well documented expectations/outcomes. Then we could use for example a Makefile to define the release process and simply use that in the pipeline

Describe alternatives you've considered
A clear and concise description of any alternative solutions or features you've considered.

Additional context
Add any other context or screenshots about the feature request here.

[harshad16]

Thanks for such a descriptive issue.
We would have to look at the base image requirement first to accommodate the release based on the script.
As the method used by the script should be available in the base image, processing that request.

[sesheta]

Issues go stale after 90d of inactivity.
Mark the issue as fresh with /remove-lifecycle stale.
Stale issues rot after an additional 30d of inactivity and eventually close.

If this issue is safe to close now please do so with /close.

/lifecycle stale

[harshad16]

/remove-lifecycle stale

[sesheta]

Issues go stale after 90d of inactivity.
Mark the issue as fresh with /remove-lifecycle stale.
Stale issues rot after an additional 30d of inactivity and eventually close.

If this issue is safe to close now please do so with /close.

/lifecycle stale

[sesheta]

Stale issues rot after 30d of inactivity.
Mark the issue as fresh with /remove-lifecycle rotten.
Rotten issues close after an additional 30d of inactivity.

If this issue is safe to close now please do so with /close.

/lifecycle rotten

[harshad16]

/lifecycle frozen