Update the Pipeline editor viz to look like Pipeline Graph

What does this MR do?

We want to change the current visualization to look more like the new pipeline graph (because it looks awesome) and so this MR is to tweak the visuals.

• Use pills similar to the pipeline graph
• Adjust the job pill width to accommodate more of the job name. Several users complained that most job names get truncated and it makes it difficult to read the graph.
• Increase the width between the columns in both pipeline graph and visualization, or rather perhaps make it dynamic so we make the lines more legible. When the columns are close to each other, when we have many lines they all look crammed and overlap much more. Of course we shouldn't make the distance too wide because some pipelines can be super wide and we don't want never ending horizontal scroll, but it has to be a balance.

Screenshots (strongly suggested)

Here is a video of everything working together

Screen_Recording_2021-06-21_at_10.26.31_AM

Here is a series of graph and what they now look like.

Pipeline visualization

Before	After

Pipeline graph stage view (No changes)

Before	After

Pipeline graph needs view

Before	After

Does this MR meet the acceptance criteria?

Conformity

• I have included changelog trailers, or none are needed. (Does this MR need a changelog?)
• I have added/updated documentation, or it's not needed. (Is documentation required?)
• I have properly separated EE content from FOSS, or this MR is FOSS only. (Where should EE code go?)
• I have added information for database reviewers in the MR description, or it's not needed. (Does this MR have database related changes?)
• I have self-reviewed this MR per code review guidelines.
• This MR does not harm performance, or I have asked a reviewer to help assess the performance impact. (Merge request performance guidelines)
• I have followed the style guides.
• This change is backwards compatible across updates, or this does not apply.

Availability and Testing

• I have added/updated tests following the Testing Guide, or it's not needed. (Consider all test levels. See the Test Planning Process.)
• I have tested this MR in all supported browsers, or it's not needed.
• I have informed the Infrastructure department of a default or new setting change per definition of done, or it's not needed.

Security

Does this MR contain changes to processing or storing of credentials or tokens, authorization and authentication methods or other items described in the security review guidelines? If not, then delete this Security section.

• Label as security and @ mention @gitlab-com/gl-security/appsec
• The MR includes necessary changes to maintain consistency between UI, API, email, or other methods
• Security reports checked/validated by a reviewer from the AppSec team

Related to #333169 (closed)