Api refactoring

[wintamute]

What do these changes do?

This PR adds a new low-level and high-level API, as discussed in #203

Currently only Images and Containers are implemented

Are there changes in behavior for the user?

All existing code is untouched, so there should be no changes in existing code

Related issue number

#203

Checklist

• I think the code is well written
• Unit tests for the changes exist
• Documentation reflects the changes
• If you provide code modification, please add yourself to CONTRIBUTORS.txt
  • The format is <Name> <Surname>.
  • Please keep alphabetical order, the file is sorted by names.
• Add a new news fragment into the changes folder
  • name it <issue_id>.<type> for example (588.bug)
  • if you don't have an issue_id change it to the pr id after creating the pr
  • ensure type is one of the following:
    • .feature: Signifying a new feature.
    • .bugfix: Signifying a bug fix.
    • .doc: Signifying a documentation improvement.
    • .removal: Signifying a deprecation or removal of public API.
    • .misc: A ticket has been closed, but it is not of interest to users.
  • Make sure to use full sentences with correct case and punctuation, for example: "Fix issue with non-ascii contents in doctest text files."

[barrachri]

@wintamute sorry for the delay, I will try to give you a feedback during the next week!

[wintamute]

@barrachri OK, I was planning on pushing another commit, fixing flake issues and one py3.5 incompatibility, it also took me longer than expected. But any feedback is appreciated

[achimnol]

I think the overall rationale of the approach looks sane:

• Having explicit DTO (data-transfer objects) with explicit schema
• Introducing hierarchical sub-package structure to better group the codes

though it's now 2024 and we need to apply new conventions such as the black code style, etc.

I'd like to keep the direction for the future, using pydantic or msgspec to add typed DTOs. However, my time resources are limited in the times other than PyCon, so it is welcome to resubmit the PR with latest CI conformance and updated practices.

Thanks!