include a post trigger in the pipeline, to trigger release in other components based on prior

[harshad16]

Is your feature request related to a problem? Please describe.
As some components depend upon the release of another component, it would be convenient if aicoe-ci can help with this process.
With a post-trigger kind of a flow in the pipeline, which enables aicoe-ci to trigger a release in another repo when a configured repo/component is successfully released.

Describe the solution you'd like
Have another task which creates the new release issue or creates a new tag in another defined repository (B), when the tag-release-run for the configured repo(A) is completed successfully.
This would start another tag-release pipeline for another component/repo B, enabling it to utilize the needs based on release of component (A)

Describe alternatives you've considered
use the sync-pipeline and hope it releases the components in the right manner 🤞

Additional context
thoth-station/thamos#599 (comment)

[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