Allow GitLab administrators to view all details of a specific scheduled pipeline without taking ownership
<!--IssueSummary start-->
<details>
<summary>
Everyone can contribute. [Help move this issue forward](https://handbook.gitlab.com/handbook/marketing/developer-relations/contributor-success/community-contributors-workflows/#contributor-links) while earning points, leveling up and collecting rewards.
</summary>
- [Close this issue](https://contributors.gitlab.com/manage-issue?action=close&projectId=278964&issueIid=520245)
</details>
<!--IssueSummary end-->
<!-- This template is a great use for issues that are feature::additions or technical tasks for larger issues.-->
### Problem
As a GitLab administrator I have to take ownership of a pipeline schedule to view all its details, including variables.
### Proposal
In GitLab [Issue #404403](https://gitlab.com/gitlab-org/gitlab/-/issues/404403), we exposed the following:
1. Cron
2. Timezone
3. Next run
4. Active State
I propose also exposing the variables that was left out while addressing the previous issue.
> And the only thing a user without edit access would not have access to in the table would be the variables. If we go this route this issue probably could be scheduled earlier since we won't need BE and FE resources.
<!-- Use this section to explain the feature and how it will work. It can be helpful to add technical details, design proposals, and links to related epics or issues. -->
<!-- Consider adding related issues and epics to this issue. You can also reference the Feature Proposal Template (https://gitlab.com/gitlab-org/gitlab/-/blob/master/.gitlab/issue_templates/Feature%20proposal%20-%20detailed.md) for additional details to consider adding to this issue. Additionally, as a data oriented organization, when your feature exits planning breakdown, consider adding the `What does success look like, and how can we measure that?` section.
-->
<!-- Label reminders
Use the following resources to find the appropriate labels:
- Use only one tier label choosing the lowest tier this is intended for
- https://gitlab.com/gitlab-org/gitlab/-/labels
- https://about.gitlab.com/handbook/product/categories/features/
-->
issue