ci: add action to enforce semantic PR titles

[Adembc]

This PR introduces a new GitHub Actions workflow to enforce semantic pull request titles for better clarity and consistency in the development process.

[jiridanek]

I think I'd prefer a conventional commit bot over this. There's 21.5k lines of Javascript in this PR, and only about 100 lines of it is handwritten, the rest are dependencies! Anyways, it does not look wrong to me, so

/lgtm

[google-oss-prow]

@jiridanek: changing LGTM is restricted to collaborators

In response to this:

I think I'd prefer a conventional commit bot over this. There's 21.5k lines of Javascript in this PR! Anyways, it does not look wrong to me, so

/lgtm

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes-sigs/prow repository.

[Adembc]

Thank you @jiridanek , for reviewing.
We discussed this issue in our last meeting and decided to create a new branch for the conventional-release-labels GHA code. @thesuperzapper will take care of this, and I will update this PR to reference it using kubeflow/notebooks/PATH@BRANCH.

[thesuperzapper]

@Adembc can you make a new PR that only does the "validate PR titles" part, because we havent really decided on the labels for release notes generation yet.

If you do that, please update to the latest version of the amannn/action-semantic-pull-request action, as there are new versions since this PR was made.

[Adembc]

@thesuperzapper done 8202eec

[thesuperzapper]

@Adembc thanks!

Lets look into a few things after this:

1. Making a similar PR into the main branch
2. Doing the "apply labels" step using the outputs feature of the amannn/action-semantic-pull-request step:
   • Remove all relevant labels, apply the ones that correspond to the type/scope.
   • We would probably need to use a custom actions/github-script, or we could use the same fork of the conventional-release-labels step as we previously were.

/lgtm
/approve

[google-oss-prow]

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: thesuperzapper

The full list of commands accepted by this bot can be found here.

The pull request process is described here

Needs approval from an approver in each of these files:

• OWNERS [thesuperzapper]

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

[Adembc]

I raised the same PR #158 into the main branch