With the release of [v13.3.0](https://github.com/semantic-release/gitlab/releases/tag/v13.3.0) of the [@semantic-release/gitlab](https://github.com/semantic-release/gitlab) plugin they have added to option to authenticate with GitLab using a CI_JOB_TOKEN, eliminating the need for a group/project/personal access token. Using the later is a pain for us, as they have to be managed on a regular basis when they expire. We are mostly using the default generated `.releaserc` from the to-be-continous semantic-release component in our projects. I therefor would like to add a new input for the component to enable the use of the CI_JOB_TOKEN by adjusting the generated default `.releaserc`. To make this feature work in general, one has to [allow Git push request to your projects](https://docs.gitlab.com/ci/jobs/ci_job_token/#allow-git-push-requests-to-your-project-repository) in the project settings. Using the CI_JOB_TOKEN has the side effect, that comments on issues and merge requests are disabled as noted by the author (https://github.com/semantic-release/gitlab?tab=readme-ov-file#using-a-ci-job-token). I have added this functionality in to-be-continuous/semantic-release!80