…llisions

References have only the table/composite type name when they belong to the `current_schema`.
If they do not, then the references have the form `<schema>.<name>`.
Affected references: Parameter Objects and Schema Objects.

* These Component Schemas are needed to build the Response Objects for functions.
* The functions returning composite types are not included since those Component Schemas are already built in another function.

* Specifies RPC arguments as query parameters, since they are needed for RPC GET requests.
* Since these arguments are different from row filters (e.g. `arg=val` not `arg=eq.val`) the original types can be used (except for objects or arrays).

* Adds media type responses for the different return types of functions (RETURNS TABLE, RETURNS <type>, INOUT/OUT arguments).
* The `application/json` media type returns `array` only when the function is `SET OF`.

* Adds "/rpc/<function_name>" endpoints for valid functions to the Paths Object.
* Valid functions are those that have no unnamed parameters or have a single unnamed parameter of type `json`,`jsonb`,`text`,`xml`. The rest are invalid.
* Only `RETURNS SET OF` functions can return `206` to a partial request.
* Common parameters such as `select`, `or`, etc. can be used when a function RETURNS TABLE, composite types or has INOUT/OUT parameters.