Rename Job Documentation improvement

[gurke]

Hi there!

I was running into a problem today.

I renamed a job today and pushed the changes on the main branch. CI somehow detected this change and triggered this "new" job, which was very unexpected, because it deployed Lambda layers to AWS.

I had a look at the documentation and found old_name, which I have not used. I guess this was the problem.

The documentation does not explain if a job get's triggered or not triggered when renaming a job.

Would like to suggest to describe this behaviour.