build: migrate packages to esm-only

`/tsconfig.esm.json` with

```json
{
"compilerOptions": {
"module": "ES2022"
}
}
```

progressive with `tsconfig.build.json` in packages with

```json
{
"extends": ["../../tsconfig.base.json", "../../tsconfig.strict.json", "../../tsconfig.esm.json"],
// ...
}
```

- [ ] `atom-sorter`
- [ ] `chemical-elements`
- [ ] `chemical-groups`
- [ ] `emdb`
- [ ] `isotopic-distribution`
- [ ] `mass-fragmentation`
- [ ] `mass-tools`
- [ ] `mf-finder`
- [ ] `mf-from-atomic-ratio`
- [ ] `mf-from-ea`
- [ ] `mf-from-google-sheet`
- [ ] `mf-generator`
- [ ] `mf-global`
- [ ] `mf-matcher`
- [ ] `mf-parser`
- [ ] `mf-utilities`
- [ ] `mfs-deconvolution`
- [ ] `ms-report`
- [ ] `ms-spectrum`
- [ ] `nucleotide`
- [ ] `number-treemap`
- [ ] `octochemdb`
- [ ] `peptide`

Start with /tsconfig.esm.json and compare the tsconfig.build.json files in the listed packages. Progressively apply the shared ESM configuration to each unchecked package, then verify that every package in the checklist is covered and its build remains valid.

Written by the indexing model from the issue text.