This adds a delete button on the profile page which when their is a
petname or an edgename is enabled and when pressed it removes any names
associated with the persona (deleing it).

There was a bug that when you would leave a name box blank or remove the
value from it it'd save it in the database as an empty string. This
would result in strange bugs like a petname snip showing with no
contents. This will now only add a petname if there is a value and
delete any name of that type if it's blank and there was a name in the
database.

This improves the .gitignore file in that it now matches on .state and
.state.root files which goblin-chat makes, instead of just the single
persona file.

It also fixes the CI by using the correct path into the hashvatar repo.
It needs to use the root of the repo, not the hashvatar code as racket
needs to install both the code and the images in order to work.

This is the initial part of supporting a contact management interface,
by refactoring out the profile page builder which defined in the
right-click menu to be a generic function which can be used anywhere
in the GUI code.

The code also takes on the role of getting the persona's sturdyref and
self proposed name and these are populated when they have been
fetched in an asynchronous fashion, not holding up drawing the entire
GUI until we have all the information.

This snip represents edgenames, it's formatted as:

     <network-graphic> <sharer-name> -> <edgename>

The network-graphic tries to convey the network/shared nature of the
name and tries to distinguish it from a petname or self-proposed-name
snip. You also pass in the type of name the sharer is for you, this
will dictate if the line around the snip is dashed or solid.

This snip probably wants improving in the future to make it more
obvious between self-proposed and petnames.

This adds a new profile page which displays an avatar based on the
persona's sturdyref. This is to help differenciate multiple people
with the same name. The user cannot choose their own avatar. This
profile page now lists their petname, edgename (you gave them) and any
edgenames shared with you for this person.

This change also adds the ability to share the edgenames, this is done
by right clicking on a user in the right hand side user list and
selecting "share edgenames".

This has renamed the "add petname" functionality to be "edit contact"
which now displays two boxes, the first for adding a petname and the
second for adding an edgename for said contact. Both are now added via
a combined "save-contact" method on the backend.

This addresses two things:

1. Don't lookup twice from the person->sturdyref cache in the
chat-backend. Store it so we can re-use it.

2. Remove unneeded pks

This requires two facets for creating and restoring sturdyref. In
normal testing those don't need to do much but for the goblin-chat-gui
main module they need to function so this puts bogus sturdyrefs into a
hash which it then retrieves from when it "enliven"s them.

The petname work needs to have `ensure-same` which verifies multiple
refrs point at the same actor. This is currently only in the git
version.

This makes petnames persistant across sessions. Now brux supports
personas having sturdyrefs, we can ask a persona for its sturdyref and
verify that it is in fact for that persona and then use that as the ID
for storing it in the petnames database. Since sturdyrefs for personas
persist across sessions this allows for petnames to be remembered and
work across sessions.

It's already in a closure!

Originally there was one object which handled observing all the
messages which came from each user.  However this resulted in
difficult to solve race conditions.  The solution, and better design,
became to have each user's chatroom presence manage its own pubsub
notifications.

There was a case where if the onion.state somehow was removed but the
chatroom.state remained an invalid sturdyref was provided to the user
when setting up the server. This was caused because the chatroom
stores the entire sturdyref and so if the machine ID changes the
sturdyref needs to change to reflect that.

This now removes the chatroom.state if the onion.state file does not
exist to avoid such problems.

This will restore a tor onion server after it has been created. When
an onion server is created for the first time, it creates a state file
for the onion data. The chatrooms used on that onion server also store
their swiss-num.

On start we now look for restorable data and if it's found, then we
restore the tor onion service and chatroom at same URL.

It was missing the current on-select method on the upper-most
hierarchical-list%. This meant that the on-select calls were not being
handled correctly. This fix now overrides that upper-most class where
the call happens and handles it correctly.

The goblin chat GUI tests were missing the persona-manager and just
passing in #f for that. This was fine at the start, however we now use
that to get the petname database and check what name to use for a
paticular persona. This now uses a mock-persona-manager from the
chat-backend.

We now need the persona-manager to provide a incanter so that you can
get the petnames database from the persona. This is used when
displaying the name of a user, to determine if you petname to display
or it should be the spn.

This reverts commit d6128806.

This adds the ability to add a petname for a contact as well as delete
them. It does not as yet off editing petnames.

Not great, but at least provide prompts where a user could fill
something in.