feat: add scss and react support in import order eslint rule

[vovakulikov]

Background

Prior to this PR, our current eslint config allowed us to have the following imports order

import { voronoi } from '@visx/voronoi'
import { noop } from 'lodash'
import React, { ReactElement, useMemo, useRef, useState } from 'react'

import styleHello from './world-styles'
import styles from './local.module.scss'
import hello from './world'

As you can see the syles imports and react imports are mixed with other group packages. Which makes the import section a bit confusing.

Since in react component React is the main import it should be the first import in the file.
Since styles import has the biggest specific to the component it should be the last import in the file.

import React, { ReactElement, useMemo, useRef, useState } from 'react'

import { voronoi } from '@visx/voronoi'
import { noop } from 'lodash'

import styleHello from './world-styles'
import hello from './world'

import styles from './local.module.scss'

[valerybugakov]

Awesome! Thank you for taking the time to update it.

The flow of fixing the errors in the codebase that I used:

1. Merge eslint-config PR.
2. New version of the config will be published to NPM.
3. Upgrade the eslint-config version in the sourcegraph repo.
4. Run eslint --fix in the sourcegraph repo.
5. Create PR with sourcegraph repo changes.
6. 🚀

Not sure what caused errors on the CI pipeline, and it seems unrelated to PR changes. Let's create an issue to investigate if re-running the pipeline doesn't help.

[sourcegraph-buildkite]

🎉 This PR is included in version 0.27.0 🎉

The release is available on:

• npm package (@latest dist-tag)
• GitHub release

Your semantic-release bot 📦🚀