Make Full Configuration tab more readable for complex pipeline scripts

Proposal

Currently, the Pipeline Full Configuration editor treats bash code as one line and adds \n instead of actual newlines which makes it very difficult to troubleshoot pipelines in the Pipeline editor.

Suboptimal Pipeline config format for bash code:

Furthermore, going to Settings -> CI/CD -> General Pipelines -> CI/CD Configuration File trying to view the Pipeline Editor -> Full Configuration to see the full pipeline file as fully assembled with all includes resolved is not possible. This makes troubleshooting very difficult as you have to manually search out each included file one at a time.

Suggested Feature:

Every time a pipeline runs there should be a new tab along with the "tests" "jobs" and "Pipeline" tab. The new tab would be something like "Pipeline Code" and when clicking on it would show the fully rendered, with all includes resolved, pipeline code that was used for that particular pipeline. Any multiline sections of code should be displayed in a readable format.

This request comes from a US Gov GitLab Ultimate customer from ZD Ticket 13536 (US Gov Access Required)