`ModuleSet`: store a set rather than a map

[9999years]

Previously, a ModuleSet wrapped a HashMap<NormalPath, TargetKind>. This had a number of undesirable consequences:

• The data about a module's name (as its path) and how it was loaded (as its TargetKind) were split from each other and difficult to reference.
• The module's import name wasn't explicitly stored anywhere, so we needed to convert between paths and dotted names when those were needed, which required hitting the disk.
• There wasn't a type for the module's import name, so when we (e.g.) :unadded modules we needed to format them as strings.

Now, a ModuleSet wraps a HashSet<LoadedModule>.

• A LoadedModule wraps a path but optionally contains the module's dotted name, if the module is loaded by name (and needs to be referred to by name to avoid the "module defined in multiple files" error).

• The LoadedModule Display instance formats the module's import name correctly (with a dotted name if needed) and avoids hitting the disk or any string processing.

• [ ] Labeled the PR with patch, minor, or major to request a version bump when it's merged.

• [ ] Updated the user manual in docs/.

• [ ] Added integration / regression tests in tests/.

[9999years]

I tried making the LoadedModule fields public and replacing ModuleSet with HashSet<LoadedModule>. The diff was +67 -148 (net -81 lines). I like the type safety and the implementation of ModuleSet has changed before, so I'm inclined to keep it at least for now.

[github-actions[bot]]

A PR to release these changes has been created, bumping the version from 1.0.0 to 1.0.1.