David/dynamic endpoints

[recalcitrantsupplant]

Specifies that "data" endpoints are defined dynamically. "Data" endpoints are what has been these endpoints:

/catalogs
/catalogs/{catalogId}
/catalogs/{catalogId}/collections
/catalogs/{catalogId}/collections/{recordsCollectionId}
/catalogs/{catalogId}/collections/{recordsCollectionId}/items
/catalogs/{catalogId}/collections/{recordsCollectionId}/items/{itemId}

These endpoints are now loaded dynamically based on RDF declarations in:
prez/reference_data/endpoints/data_endpoints_default

To instead use custom endpoints, follow the instructions in the README-Custom-Endpoints.md

In summary Prez will:
If CUSTOM_ENDPOINTS is "true":

• look for endpoints in the data repo (e.g. triplestore), and if declarations are found, dynamically load these
• if no definitions are found, the local directory is checked prez/reference_data/endpoints/data_endpoints_custom, and if declarations are found, these are dynamically loaded.
  If CUSTOM_ENDPOINTS is unset or any other value:
• the endpoints defined in prez/reference_data/endpoints/data_endpoints_default are loaded.

[lalewis1]

still testing but initial note:

it has created the endpoints dynamically but when I browse the /catalogs endpoint no data is shown even though the target class is dcat:Catalog and there are dcat:Catalog 's defined in the data (and the catalogs do have dcat:Resource 's in them related via dcterms:hasPart)

nevermind, it does this on main branch too. must be something with my data.

[lalewis1]

looks good. just pushed a small commit to fix the relative path not resolving in my environment (for the static files folder)