feat(@stylexjs/eslint-plugin): Accept { from: string, as: string } syntax in validImports option for RSD

[javascripter]

What changed / motivation ?

React Strict DOM recently removed their eslint plugin and I'm considering migrating to @stylexjs/eslint-plugin.

However, react-strict-dom exports stylex under css object, and it is it incompatible with current validImports option in the eslint plugin.

e.g. This doesn't work:

module.exports = {
  plugins: ['@stylexjs'],
  rules: {
    '@stylexjs/sort-keys': [
      'error',
      {
        validImports: ['react-strict-dom']
      },
    ],
  },
};

I have added { from: string, as: string } syntax similar to importSources option in the babel plugin for compatibility with RSD, for both @stylexjs/sort-keys and @stylexjs/valid-styles rules.

e.g. now the option accepts this format:

{
  validImports: [
    {
      from: 'react-strict-dom',
      as: 'css',
    },
  ],
},

Additional Context

• Added unit tests
• Updated the api docs
• I also checked the behavior locally in apps/nextjs-example dir by replacing imports with react-strict-dom and configuring with the new options as in the screenshot.

Pre-flight checklist

• I have read the contributing guidelines
  Contribution Guidelines
• Performed a self-review of my code

[javascripter]

foundImportSource will be either a string or the object containing "as" and "from".

[javascripter]

Then, if foundImportSource is a string,styleXDefaultImports and the other variables will be updated exactly the same as before.

[javascripter]

If using the new as and from syntax, we will treat the value of the as option as the default import name. This is because the resolution mechanism is the same as import stylex from 'xxx', where the property names of stylex are fixed to create, props, etc, and the same constraints apply to the css object as well.

import { css } from 'a'

[necolas]

@nmn You approved this PR but it wasn't merged. Is there something else that needed work?

[necolas]

See #1039 for this PR rebased on main