split OGC Features and Tiles endpoints factories

[vincentsarago]

closes #6

This PR split the endpoint factory in two: OGCFeaturesFactory and OGCTilesFactory which should enable user to build either the tiles service or features service individually.

The main issue is for creating the OGC features landing and conformances endpoints. I've added two ways:

• within the OGCFeaturesFactory, by using the full=True option, this will add the / (landing) and /conformance endpoints but only referencing the features endpoint (no links to the Tiles endpoints).

  from tipg.factory import OGCFeaturesFactory
  from fastapi import FastAPI
  
  app = FastAPI(
      openapi_url="/api",
      docs_url="/api.html",
  )
  features = OGCFeaturesFactory(full=True)
  app.include_router(features, tags=["OGC Features API"])

• in main.py, to have both tiles and features endpoints conformances and links. It is likely that a user who will want to add both / (landing), /conformance with tiles and features endpoints in it's own application will have to re-write both endpoints in its code 🤷‍♂️

IMO it's really annoying that both / and /conformance are part of the features specification 😬

[vincentsarago]

@bitner any of this make sense? 😄

[vincentsarago]

latest version of FastAPI/starlette changed something in url_for https://github.com/encode/starlette/pull/2050 which breaks tipg (and other project where I use url_path_for 😬 ) 🤷

[vincentsarago]

😬 it's the output of url_for which was a string before and now is of type URLpath

see https://github.com/encode/starlette/pull/1385

[vincentsarago]

last commit refactored a bit how we add the OGC common endpoints. It's now defined at the base class level.

To Do

• [x] add tests for each Factory

[vincentsarago]

@bitner this is ready 🙏