Input arbitrary stars as oracles

Currently the oracle list is manaully maintained. This is fine for a recommended list, but it creates a snag for new oracle users who are excited about using their newfound powers. We should update the interface to support entry of any galaxy or star level identities.

Base behavior is to be able to type in any eligible @p and have them serve as your oracle.

There are a few edge cases / ux hurdles to consider here:

1. users will be able to enter an non-running, un-booted ship.
2. given this, do we want to limit the list to "stars and galaxies that have an updated version of %fund installed from ~tocwex?
3. what would it take to have a connectivity indicator similar to what tlon uses? could we do a 'dumber' version of these to just check the last packet sent to that address and if it isn't w/in the same day, hide that entry? This seems hamfisted, but directionally correct.

Start by tracing the manually maintained oracle list and the interface where oracle identities are entered. Define how arbitrary eligible @p identities should be accepted, then resolve the behavior for unbooted ships and whether a last-packet connectivity indicator or installed-version requirement is needed before implementation.