Fixes #19.

Add CI to publish project to maven.

- fix a bug where here(xyz) loses access to the correct up
- fix the API so that calls to here/up do not need a 'site' supplied
- documentation for functions added

* add mill support

* add gitignore and remove pom.

Everyone gets confused by the order of ++.
It's backwards from what people expect.

When you name your Configs 'WithX' it gets especially confusing.
People want to write: Base ++ WithX ++ WithY, but that's wrong!
They actually need: WithY ++ WithX ++ Base.

The API: x.alter {
  case X => Y
}
... does work as people expect. Right-hand side wins.

Let's encourage people to write this:
  Base alter WithX alter withY

Later we can deprecate '++' so people can write:
  WithY orElse withX orElse Base

* CI: add a github actions rule to type check the repository

* wit-manifest: bump to head of api-scala-sifive for 0.18 support

* CI: actually compile using wake and SBT

* CI: remove legacy travis build rules

* Revert "CI: actually compile using wake and SBT"

This reverts commit 3f913db1f834198d6ac37d55a0ce23b08113b709.

* CI: try actually building it

* CI: add sbt compile back to flow

add .gitignore

Add license file and rename package

Also rename some keys that had the same class name as their value's class name.

This has been good practice for ages. Enforce it.

* Refactors package hierarchy.

Additionally:
  - Removes legacy ground tests and configs
  - Removes legacy bus protocol implementations
  - Removes NTiles
  - Adds devices package
  - Adds more functions to util package

* Configs: use a uniform syntax without Match exceptions

The old style of specifying Configs used total functions.  The only way to
indicate that a key was not matched was to throw an exception.  Not only was
this a performance concern, but it also caused confusing error messages
whenever you had a match failure from a lookup within a lookup.  The
exception could get handled by an outer-lookup that then reported the wrong
key as missing.