Redesigning Poetry's Schema Handling

[abn]

poetry-schema.json: I noticed that both projects (poetry and poetry-core) carry a schema file. Is that really required? I guess we could have only one file in poetry-core and be consumed by poetry when/if required.

Originally posted by @wagnerluis1982 in #4776 (comment)

[abn]

The poetry version of the schema is a hangover from before splitting out poetry core and should be removed and only extensions (or things that do not make sense in core) be defined in poetry.

[wagnerluis1982]

It seems to me that the sole place which the schema is used is at the function from poetry.json import validate_object, the link below show the exact point I traced the usage.

poetry/src/poetry/json/__init__.py

Line 18 in 7c53db9

schema = os.path.join(SCHEMA_DIR, f"{schema_name}.json")

Thing is, there is NOT a single USAGE to the function validate_object, in fact I removed completely from the working dir the folder src/poetry/json/ and run pytest, not a single test has failed. Which indicates to me the poetry-schema.json is being uselessly updated in poetry on the last months (more than 6 months at least).

[neersighted]

Please feel free to submit a PR deleting the file/references -- it indeed is just dead weight.