feat: update to Stylelint v15

[dstaley]

🎟️ Asana Task

---

Description

This PR updates Stylelint in platform-cli to the latest version to ensure compatibility with the latest versions of CSS.

PR Checklist 🚀

• Conduct thorough self-review.
• Add or update tests as appropriate.
• Write a useful description (above) to give reviewers appropriate context.
• Identify (in the description above) and document (add Asana tasks on this board) any technical debt that you're aware of, but are not addressing as part of this PR.

[changeset-bot]

🦋 Changeset detected

Latest commit: 06af1d3

The changes in this PR will be included in the next version bump.

This PR includes changesets to release 1 package

Name	Type
@hashicorp/platform-cli	Major

Not sure what this means? Click here to learn what changesets are.

Click here if you're a maintainer who wants to add another changeset to this PR

[github-actions]

📦 Canary Packages Published

Latest commit: 06af1d3

Published 1 packages

@hashicorp/platform-cli@3.0.0-canary-202361820465

npm install @hashicorp/platform-cli@canary

[thiskevinwang]

Just so I'm following, what is the explanation for removal of

• stylelint-config-prettier
• stylelint-media-use-custom-media
• stylelint-value-no-unknown-custom-properties

[dstaley]

The first one isn't necessary anymore, and the latter two are not compatible with v15. I figured we can probably live without those two for now and add them back when/if they update for v15.

[thiskevinwang]

Looks reasonable to me! Left a non-blocking question

[dstaley]

@thiskevinwang looks like we'd need to disable a good chunk of rules to prevent auto-fixes on www.

    // we don't enforce a standard naming pattern
    'selector-class-pattern': null,
    'keyframes-name-pattern': null,
    'custom-property-pattern': null,

    // we didn't previously limit numerical precision
    'number-max-precision': null,

    // we didn't previously enforce empty lines
    'at-rule-empty-line-before': null,
    'custom-property-empty-line-before': null,
    'declaration-empty-line-before': null,
    'rule-empty-line-before': null,

    // we
    'declaration-block-no-redundant-longhand-properties': null,
    'shorthand-property-no-redundant-values': null,
    'media-feature-range-notation': null,
    'color-function-notation': null,
    'alpha-value-notation': null,
    'import-notation': null,
    'function-url-quotes': null,
    'property-no-vendor-prefix': null,
    'value-no-vendor-prefix': null,
    'at-rule-no-vendor-prefix': null,

A few rules are dumb imo (such as declaration-block-no-redundant-longhand-properties which collapses properties into the shorthand form), but since all of these can be automatically fixed, I kind of think it'd be worthwhile to examine what rules we'd like to keep.