Json.getPath signature

Hi,

I'll begin by saying, amazing library, thank you!

I've looked at the `getPath` signature and started wondering whether it wouldn't be nicer if it had the following signature: `list(string) => option(string) = ;`

It would mean less parsing in the library and support for crazy json authors who include `.` in their keys.

This is all a bit inspired, by how Ramda does it: https://ramdajs.com/docs/#path

Thanks!

Start by locating the getPath definition and any tests covering JSON path parsing. Compare the current signature with the proposed list(string) => option(string) API and check how keys containing dots should be handled. Done means the API supports those keys without breaking existing path behavior.

Written by the indexing model from the issue text.