Introduce the mappings feature

[HU90m]

Introduce the mappings feature discussed in #727. See #727 (comment) for context.

Description of the feature from the documentation:

Mappings allow a user of a core to substitute dependencies of the core with other cores without having to edit any of the core or it's dependencies files. An example use case is making use of an existing core but substituting one of it's dependencies with a version that some desired changes (e.g. bug fixes).

I've restricted the flexibility of mappings in the interest of keeping this patch set smaller:

• They cannot be recursive.
• They cannot include versions.
• Cores conflicting with substitutes aren't removed from the dependency tree.
  • For OpenTitan's use case, a flag can be used to disable the default primitives so there are no conflicts.

These restrictions can be lifted in the future commits, if deemed useful.

The commits are all self contained: lints and tests pass for every commit, so they don't need to be squashed. However, re-ordering may make sense.

[olofk]

Very nice and clean set of commits. A+ :) I agree with the limitations. It's better to start small and then we can expand if needed, rather than promising too much to begin with. Picked and pushed! Many thanks for your contributions.

[olofk]

There's one potential feature I could be interested in, and that's the possibility to set single mapping directly on the command line, e.g. --map some:virtual:core some:specific:core but it's more of a convenience than anything strictly needed.