Handle position encodings

New versions of the spec have position encoding negotiation. We could handle this as follows:
- Allow the user to set a (list of?) preferred encodings
- Send the most preferred one which the client accepts to the client
- Store the encoding in the state
- Use the stored encoding to affect how we translate positions in the VFS, this would let us do less work in some situations