Remove import/first[absolute-first] in favor of import/order about eslint-config-fusion

[rickyp-uber]

import/sort does not order by path, it orders by first specifier based on documentation which isn't ideal considering your imports may jump around in diffs if you import a new function (e.g. importing extra lodash functions).

I'm also curious what the benefit of enforcing the ordering actually is. If a team wants to enforce it they can, but in the base eslint rules? Why? I say just enforce the import/first without absolute and avoid bad code scenarios from a platform perspective. As for ordering preferences, leave that up to each team.

[rickyp-uber]

Oh and if you're enforcing the sort order of imports, may want to include exports in that ordering then
and change import/exports-last to on instead of off (which is it's current value)

[rickyp-uber]

About import/first... Jest allows you to mock an import, for example:

jest.mock('@uber/web-rpc-redux');
import * as rpcRedux from '@uber/web-rpc-redux';

Without adding a eslint-disable for every single one of these cases, is there a more general solution if we keep import/first?

[KevinGrandon]

I think we've decided as a team that we only want to go with eslint:recommended and type checking for now. Developers can be more specific with their own rules if they want.

[rickyp-uber]

Is there a issue/PR tracking the work to remove the non eslint:recommended rules that have already been added?