no-named-as-default-member rule is broken in specific cases

import/no-named-as-default-member is broken in such a case:

// id-values-map.js

const ID_VALUE_MAP = {
  x: 4,
  y: 14,
};

const DEFAULT_ID = 'x';

export default ID_VALUE_MAP;
export { DEFAULT_ID };

// usage.js

import ID_VALUE_MAP, { DEFAULT_ID } from './id-values-map';

use(ID_VALUE_MAP[DEFAULT_ID]);
// ESLint: Caution: `ID_VALUE_MAP` also has a named export `DEFAULT_ID`. Check if you meant to write `import {DEFAULT_ID} from './id-values-map'` instead.(import/no-named-as-default-member)

Reproduce the warning using the id-values-map.js and usage.js examples in the issue, then trace the import/no-named-as-default-member rule and its existing tests. The fix is done when importing the default object and accessing it with the named export no longer produces this false-positive warning, with a regression test covering the example.