Fix user and trigger-request variables for pipeline seed
What does this MR do and why?
In the previous MR (!161881 (merged)), we improved the variable calculation performance by decoupling the job object from the process. It turned out that we did not pass the user and trigger_request objects correctly.
User report: #470827 (comment 2065434412)
In this change, we are passing them from the build context and test them correctly.
MR acceptance checklist
Please evaluate this MR against the MR acceptance checklist. It helps you analyze changes to reduce risks in quality, performance, reliability, security, and maintainability.
Related to #350057 (closed)
Edited by Furkan Ayhan