Updates to data_path and entries in optimade.yaml format

[unkcpz]

No description provided.

[ml-evs]

This PR now updates the config file format to pass through the archive path, and then uses it for the IDs as discussed in #15

[eimrek]

Couple of modifications:

• removed the option of specifying data_paths, just to prevent potential confusion/mismatch.
• adapted archive scripts
• added the {"x-optimade": ...} header
• fixed the structures id (previosly, it included the full path on the machine (e.g. /tmp/...)

ran this version on the new staging-archive entry and everything seems fine (http://dev-optimade.materialscloud.org/archive/rj-sy)

[ml-evs]

Couple of modifications:

* removed the option of specifying `data_paths`, just to prevent potential confusion/mismatch.

* adapted archive scripts

* added the `{"x-optimade": ...}` header

* fixed the structures id (previosly, it included the full path on the machine (e.g. `/tmp/...`)

ran this version on the new staging-archive entry and everything seems fine (http://dev-optimade.materialscloud.org/archive/rj-sy)

Thanks @eimrek, looks great! The JSONL dump is still missing the info endpoints and custom properties (from my side) but I think we should merge this.

[eimrek]

thanks @ml-evs. just to mention that the header is skipped in data injection of optimade-launch, so i added it in an ad-hoc manner just to prevent skipping a structure. Should be refactored, probably.