📖 Improve clarity of prowjob configuration regeneration instructions

[Sunnatillo]

What this PR does / why we need it:
Adds more explanation on how to generate prowjob configuration on release-tasks.md file

Area example:
/area documentation

[k8s-ci-robot]

Hi @Sunnatillo. Thanks for your PR.

I'm waiting for a kubernetes-sigs member to verify that this patch is reasonable to test. If it is, they should reply with /ok-to-test on its own line. Until that is done, I will not automatically test new commits in this PR, but the usual testing commands by org members will still work. Regular contributors should join the org to skip this step.

Once the patch is verified, the new status will be reflected by the ok-to-test label.

I understand the commands that are listed here.

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/test-infra repository.

[Sunnatillo]

/assign @chrischdi

[adilGhaffarDev]

/ok-to-test

[chrischdi]

/lgtm
/approve

[k8s-ci-robot]

LGTM label has been added.

Git tree hash: 7f808e45dd89d50f8cd0a87a2192ed5837a3ee5c

[k8s-ci-robot]

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: chrischdi

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:

• docs/release/OWNERS [chrischdi]

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

[sbueringer]

Totally fine as is, but in general let's try to not link too much to PRs for documentation and rather properly document things. It's a bit annoying to have to go through PR diffs to gather additional context.

(it's fine for prior art and in some other cases. It just becomes annoying over time if we use this too much)