Entity migration to spire

[kompotkot]

Changes

The archetecture with separate Entity API service showed weaknesses in response time. So in order to imcrease spead of communications with journal-based services we decided to merge Entity API to Spire API.

Here representation approach. Where we not modify original database structure of journals with entites and return formatted reposnse depends on user request.
During iteraction with Journal Spire API client call endpoints journals/ or collections/ depends what representation of journal entries they expect:

class JournalRepresentationTypes(Enum):
    COLLECTION = "collection"
    JOURNAL = "journal"

After it response will be returned based on representation.

How to test these changes?

Tested locally

Related issues

[kompotkot]

@bugout-dev check

• Migrate all main Entity API endpoints
• Migrate all public Entity API endpoints
• Set AWS routing to Spire API
• Add env variables from Entity API to be availabe at Spire API machines
• Update python client of Entity API
• In EntitySearchResponse modified entities -> results as in original search response
• In EntityResponse modified entity_id -> id as in original response