Support APIs/Services as an entity

Is your feature request related to a problem? Please describe.

“We hooked up lineage to airflow and it has been working flawlessly so far. What we have is that some tasks will fetch data from an API Rest and save this data in a database, having inlets as the api and outlets as the database. I can declare the outlet with a Dataset() obj, but how would I go about the API (inlet)? Should I declare it as a dataset or is there a more specific keyword that will mark it as an api in the UI?” - Slack

Describe the solution you'd like

Ability to ingest APIs/services as an entity; create lineage linkages to other metadata entites

Describe alternatives you've considered

Assign APIs/services as a “Dataset” entity