Making `ExportMap` available in `eslint-module-utils`?

The `ExportMap` generally makes possible lint rules which evaluate metadata in files/nodes imported by the "current" file. For example, the [import/no-deprecated](https://github.com/import-js/eslint-plugin-import/blob/main/docs/rules/no-deprecated.md) rule uses it to check for `@deprecated` doc tags for any imported items.

This is a powerful utility, and could be used to condition other custom rules--e.g., perhaps by looking at _different_ doc tags, or looking at other node metadata entirely.

Would you be open to a PR that exposes `ExportMap`/`ExportMapBuilder` in the `eslint-module-utils` package like is done for the `moduleVisitor` utility?

Thanks!

Start by inspecting how the moduleVisitor utility is exposed through the eslint-module-utils package. Then trace the existing ExportMap and ExportMapBuilder definitions and package entry points to determine the required public exports. Done means both utilities are available to package consumers, with relevant existing tests updated or added.

Written by the indexing model from the issue text.