Increase rule escalation rule arrow for each next rule

What does this MR do?

Updates styling of the escalation rule arrow to grow in size with each next rule. Arrow is NOT increased proportionally with the elapsed time just some constant increase for the visual distinction of each next rule in priority.

The minimal license required is GitLab Premium

To check - navigate to your project=>Operations=>Escalation Policies.

Create an escalation policy with a couple of rules (max 10 - the limit is added in another MR). Notice that each next arrow in the policy display is larger.

⚠ If schedule dropdown in add policy modal is disabled - navigate to your project=>Monitor=>Oncall-schedules to create a schedule or several

Screenshots or Screencasts (strongly suggested)

Viewport size change

Action tooltip

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 #333107 (closed)