[ioan-alexandra]

Closes #142

simdb manifest check (and simulation ingest) now report where a manifest is wrong:

Error: invalid manifest test.yaml (2 errors):
  test.yaml:5:5: outputs[0].uri: URL scheme should be 'file' or 'imas'
  test.yaml:6:1: bogus: Extra inputs are not permitted

• YAML syntax errors keep the parser's reason and line/column instead of badly formatted manifest.
• Validation errors are mapped back to the source line of the offending key or list item, sorted in file order, without pydantic's type/url noise.
• Metadata entries are validated individually, so errors name the entry (metadata[1]).
• load_from_file raises a new InvalidManifestError(ValueError) instead of pydantic's ValidationError.

Follow-ups: "No files found matching path" has no line number.

[prasad-sawantdesai]

Seems fine

$ simdb manifest create valid.yaml
$ simdb manifest check valid.yaml
Error: invalid manifest valid.yaml (1 error):
  valid.yaml: No files found matching path /home/user/path/to/a/file1

[prasad-sawantdesai]

LGTM..

$ simdb manifest check manifest_1210250004.yaml         
ok

[olivhoenen]

It looks good @ioan-alexandra, but could you also check against duplicates URIs (file or imas) between inputs and outputs sections?

[ioan-alexandra]

It looks good @ioan-alexandra, but could you also check against duplicates URIs (file or imas) between inputs and outputs sections?

added now. one note is because of how pydantic validates a model (first the field and then the model validations) the duplication error is only going to show when there's no other field error