feat: Setup basic FastAPI project

[aadarsh-ram]

Fixes #6

What

• Setup of basic FastAPI project, with a few endpoints
• Dockerfile setup for the backend API
• Docs containing Docker setup process
• Creation of a JSON schema for a taxonomy
• Creation of a JSON file for a test taxonomy

Part of

[alexgarel]

@aadarsh-ram just a comment to already structure the project.

[aadarsh-ram]

@alexgarel Please review this PR, and let me know your comments.

[alexgarel]

@aadarsh-ram, good work.

I'm not ok with your shema.json and test.json, but let's merge first, for this is another problem.

For me we have to work with the neo4j database, maybe I should provide you with the sample data to import in neo4j which correspond to test.txt

[alexgarel]

Kudos for having wrote this test. This will be usefull to @BryanH01 also, I guess.

[alexgarel]

I won't argue over the need of this schema.json, I really think we will do it all in the neo4j database. But let's get them in, for now we shall see later.

However there are mismatches with the spec.

For example:

• "preceding_lines" is a list of strings.
• no __comments__ block is mentionned
• stopwords:IDX and synonyms:IDX are distinct nodes from __header__
• etc.

But your schema has it's own logic per se… it's more than we must align :-)

Maybe we should better discuss the neo4j schema (in facts it's schema less) and have the equivalent of test.txt as an importable file.

[aadarsh-ram]

Yep, sure! We'll discuss the structure of JSON, and bring a unified schema.