Clients are stored with invalid predicates

Describe the bug

tl;dr: The data in the 'person' field on users doesn't comply with the schema.org spec.

Currently, the client list is storing clients in the userlist.ttl file on client pods with a format like the following:

<#http%3A%2F%2Flocalhost%3A3000%2Ftimbot%2Fprofile%2Fcard%23me>
    <http://schema.org/Person> "New Person";
    <http://schema.org/givenName> "New";
    <http://schema.org/familyName> "Person";
    <http://schema.org/identifier> <http://localhost:3000/timbot/profile/card#me>;
    <http://schema.org/URL> <http://localhost:3000/timbot/>.

This incorrectly handles the http://schema.org/Person predicate. We are using it as if it were a field, but it is actually a type. It is meant to describe what values the object holds, not hold a value itself. What we want to say here "this contact, identified by the URI, is a person, and they have the name "New Person"." However, what we're actually saying is "this contact, identified by the URI, persons the text "New Person."

Requested Fix

Rewrite the structure of the contacts list so that it is stored with valid RDF data.

A valid structure would be something like:

<#http%3A%2F%2Flocalhost%3A3000%2Ftimbot%2Fprofile%2Fcard%23me>
    a  <http://schema.org/Person>;
    <http://schema.org/givenName> "New";
    <http://schema.org/familyName> "Person";
    <http://schema.org/identifier> <http://localhost:3000/timbot/profile/card#me>;
    <http://schema.org/URL> <http://localhost:3000/timbot/>.

Note that instead of using http://schema.org/Person as a predicate, it uses a as the predicate, and http://schema.org/Person as the object. The a predicate is a reserved term in TTL. You can read more about it here

Another valid approach would be to remove the Person entry altogether.

Additional context
Most of the behavior about the contacts list is handled in src/hooks/useContactsList.js. That would be a good place to start looking for how to fix this