Rename job trace to job log in code

What does this MR do and why?

We renamed job trace to job log in GitLab 12.5, but we still often use the term trace internally because our code still uses the legacy name. This MR changes the term trace to job log in our code grouppipeline execution .

Related to: #340627 (closed)

Screenshots or screen recordings

No visual changes, just need to ensure the feature still works as intended.

How to set up and validate locally

This MR aims to just change the term trace to job log in our code for the job log feature. So code around jobs in general.

To test this have a job on your local GDK and ensure nothing is broken with the feature from this re-name. Also for the re-names you could pull down this branch and ensure that something re-named still doesn't exist in the code that hasn't been properly re-named.

MR acceptance checklist

This checklist encourages us to confirm any changes have been analyzed to reduce risks in quality, performance, reliability, security, and maintainability.

• I have evaluated the MR acceptance checklist for this MR.

Related to #340627 (closed)