Pull in filenames/match-exported

```js
// Considered problem only if the file isn't named foo.js or foo/index.js
export default function foo() {}

// Considered problem only if the file isn't named Foo.js or Foo/index.js
module.exports = class Foo() {}

// Considered problem only if the file isn't named someVariable.js or someVariable/index.js
module.exports = someVariable;

// Never considered a problem
export default { foo: "bar" };
```

https://www.npmjs.com/package/eslint-plugin-filenames#matching-exported-values-match-exported

Start with the match-exported rule documentation at the linked npm package and compare its examples with the desired behavior in this issue. Then locate the repository's ESLint rule configuration and related tests, and verify that exported functions, classes, and variables are checked against filenames while exported objects are ignored.

Written by the indexing model from the issue text.