feat(css): add gl-max-w-0

What does this MR do?

Add gl-max-w-0 utility class. Related to #2098 (closed)

Does this MR meet the acceptance criteria?

Conformity

• Code review guidelines.
• GitLab UI's contributing guidlines.
• If it changes a Pajamas-compliant component's look & feel, the MR has been reviewed by a UX designer.
• If it changes GitLab UI's documentation guidelines, the MR has been reviewed by a Technical Writer.
• If the MR changes a component's API, integration MR(s) have been opened in the following projects to ensure that the @gitlab/ui package can be upgraded quickly after the changes are released:
  • GitLab: mr_url
  • CustomersDot: mr_url
  • Status Page: mr_url
• Added the ~"component:*" label(s) if applicable.

Security

If this MR contains changes to processing or storing of credentials or tokens, authorization and authentication methods and other items described in the security review guidelines:

• Label as security and @ mention @gitlab-com/gl-security/appsec
• Security reports checked/validated by a reviewer from the AppSec team

Accessibility

If this MR adds or modifies a component, take a few moments to review the following:

• All actions and functionality can be done with a keyboard.
• Links, buttons, and controls have a visible focus state.
• All content is presented in text or with a text equivalent. For example, alt text for SVG, or aria-label for icons that have meaning or perform actions.
• Changes in a component’s state are announced by a screen reader. For example, changing aria-expanded="false" to aria-expanded="true" when an accordion is expanded.
• Color combinations have sufficient contrast.

Closes #2098 (closed)

added Leading Organization label

Hey @ali_o_kan!

Thank you for your contribution to GitLab. Please refer to the contribution flow documentation for a quick overview of the process, and the merge request (MR) guidelines for the detailed process.

When you're ready for a first review, post @gitlab-bot ready. If you know a relevant reviewer(s) (for example, someone that was involved in a related issue), you can also assign them directly with @gitlab-bot ready @user1 @user2.

At any time, if you need help, feel free to post @gitlab-bot help or initiate a mentor session on Discord. Read more on how to get help.

To enable automated checks on your MR, please configure Danger for your fork.

You can comment @gitlab-bot label <label1> <label2> to add labels to your MR. Please see the list of allowed labels in the label command documentation.

This message was generated automatically. You're welcome to improve it.

added Community contribution workflowin dev labels

assigned to @ali_o_kan

Important: This MR may be part of the running Hackathon! Check out the Hackathon page to see if it is eligible for a chance to win a prize!

This message was generated automatically. You're welcome to improve it.

added Hackathon label

@gitlab-bot label typemaintenance maintenancerefactor frontend

added frontend maintenancerefactor typemaintenance labels

@gitlab-bot ready @jiaan

added workflowready for review label and removed workflowin dev label

requested review from @jiaan

@jiaan, this Community contribution is ready for review.

• Do you have capacity and domain expertise to review this? We are mindful of your time, so if you are not able to take this on, please re-assign to one or more other reviewers.
• Add the workflowin dev label if the merge request needs action from the author. This message was generated automatically. You're welcome to improve it.

added devopsmanage groupfoundations labels

added sectiondev label

approved this merge request

mentioned in issue #2098 (closed)

requested review from @ohoral and removed review request for @jiaan

resolved all threads

Minor release (conventional commits)

This Merge Request will trigger a minor release of GitLab UI, triggered by commit: b971b7a9

This will bump the second part of the version number, e.g. v1.2.3 -> v1.3.0.

Reviewer roulette

Changes that require review have been detected! A merge request is normally reviewed by both a reviewer and a maintainer in its primary category and by a maintainer in all other categories.

To spread load more evenly across eligible reviewers, Danger has picked a candidate for each review slot. Feel free to override these selections if you think someone else would be better-suited or use the GitLab Review Workload Dashboard to find other available reviewers.

To read more on how to use the reviewer roulette, please take a look at the Engineering workflow and code review guidelines. Please consider assigning a reviewer or maintainer who is a domain expert in the area of the merge request.

Once you've decided who will review this merge request, mention them as you normally would! Danger does not automatically notify them for you.

Category	Reviewer	Maintainer
frontend	Kushal Pandya (@kushalpandya) (UTC+5.5)	Mark Florian (@markrian) (UTC+0)

If needed, you can retry the danger-review job that generated this comment.

Generated by Danger

enabled automatic add to merge train when the pipeline for 26c503df succeeds

approved this merge request

started a merge train

merged

mentioned in commit d86d8dbf

@ali_o_kan, how was your code review experience with this merge request? Please tell us how we can continue to iterate and improve:

1. React with a or a on this comment to describe your experience.
2. Create a new comment starting with @gitlab-bot feedback below, and leave any additional feedback you have for us in the comment.

Interested in learning more tips and tricks to solve your next challenge faster? Subscribe to the GitLab Community Newsletter for contributor-focused content and opportunities to level up.

Thanks for your help!

This message was generated automatically. You're welcome to improve it.

mentioned in merge request gitlab!112177 (merged)

added linked-issue label