RD-8272 implement json infer and parse

[alexzerntev]

• Added Json.InferAndParse . For this entry a new sources package had to be built called raw-sources-in-memory . It implements ByteStreamLocation traits and instead of reading from URL like other Location objects, it reads directly from memory. The schema for it is called in-memory:.
• Fixed some warnings
• Removed deprecated sparkUrl field in Locations

[miguelbranco80]

I'm torn here. I know we discussed it and agreed, but I'm wondering if we shouldn't instead have in-memory be a base64 string encoding of a binary? In that case, the data would be in the URL itself. It's probably silly and slower so will leave it at your discretion.
If we'd like to expose "in-memory" locations to users, how would that look like?

[alexzerntev]

I'm wondering if we shouldn't instead have in-memory be a base64 string encoding of a binary
Seems the same to me, but if the string is large enough maybe we will have extra encode-decode overhead.

If we'd like to expose "in-memory" locations to users, how would that look like?
JsonInferAndRead("in-memory://" + Base64.Encode("data"))

JsonInferAndRead(InMemoryLocation.Build(string data, string encoding))

Something like that? But seems a little complex.