Deprecate /node/full/{path} routes

[danielballan]

Until #478, the word "node" in tiled has two meanings:

1. every node the in the logical "tree" of tiled's data model
2. specifically, a container-like structure

In #478, we introduced the term container for (2). Now, every object in tiled in a "node", and every node has a "structure family" which may be container or table or array or ...

The routes GET /node/full/{path} and PUT /node/full/{path} are vestigial, from this legacy. They operate on both container and table structures, which have similar semantics, in that they can both be filtered by fields/columns.

This PR leaves the routes in place, for full backward-compatibility, but adds new routes:

GET /table/full/{path}
PUT /table/full/{path}
GET /container/full/{path}

(The omission of PUT /container/full/{path} is intentional. Putting container data has never been supported, but is planned.)

It updates the Python client to use these new routes.

The goal of this change is:

• Reduce potential confusion about the meaning of "node"
• Provide a memorable URLs: /table/full/... for getting a table is more natural than /node/full/....
• Lay track for future divergence of the query parameters support for containers and tables. The semantics are broadly similar, but I can easily imagine growing support for parameters than only apply to one or the other.

[padraic-shafer]

I had imagined that the python client relied on the generic node/full/{path} route for implementing __getitem__(). On inspection, it appears that it instead uses the self.links attribute to find the correct URL path.

Is that correct?

[danielballan]

Yes, correct. To elaborate, /node/full (and now /container/full) is for downloading all the data+metadata below a given point in the logical tree as a big file---some format like HDF5 or JSON that can represent nested structures.

The __getitem__ method is using JSON descriptions from the /search and or /metadata routes, and it obtains the URLs from self.links.

[padraic-shafer]

Thank you for making these clarifying changes to the HTTP API.