chore: declare version range for peer dependencies

[sapphi-red]

Description

Specified the peer dependencies version range.
Previously, we used *, which didn't clearly communicate which versions were actually supported. For example, #19977 requires sass 1.45.0+ and #19978 requires sass 1.70.0+, but this isn't obvious from the current package.json and it wasn't clear whether relying on which feature would require a major version.

Here's the reasoning behind the chosen ranges for each peer dependency:

• less: selected range ^4.0.0
  • actually, less 2.1.0 worked
  • it would be better to have it at least ^3.8.0 || ^4.0.0 because rewriteUrls feature was introduced in 3.8.0 which we might use in the future
  • but since 4.0.0 was released 5 years ago (2020-12-18), I guess it's fine to require that
• sass: selected range ^1.70.0
  • modern API was introduced in 1.45.0 so this is the lowest version for refactor(css)!: remove sass legacy API support #19977
  • compiler API was introduced in 1.70.0 so this is the lowest version for refactor(css)!: always use sass compiler API #19978
  • while there're some breaking changes between 1.45.0 - 1.70.0, but I think the benefits of refactor(css)!: always use sass compiler API #19978 justifies it
• stylus: selected range >=0.54.8
  • deps list support was introduced in 0.43.0 (we use it for watching the imported files)
  • source map support was introduced in 0.48.0
  • but I think we go with 0.54.8+ because when using a version before that, many warnings are shown (Fix for Node v14 'Accessing non-existent property' errors stylus/stylus#2538)
  • stylus uses 0.x versions. I used >= so that we don't need to keep adding || ^0.x to the range
• sugarss: selected range >=5.0.0
  • 2.0.0 uses postcss v7 and 3.0.0+ uses postscss v8 (Vite uses postcss v8)
  • we can support ^3.0.0 || ^4.0.0 || ^5.0.0 without much burden. But the breaking changes between them are only dropping Node versions older than 16, so probably ok to simply go with ^5.0.0