Provide Python bindings

Nobody has claimed this yet.

### Summary
Provide python bindings for the api. Bindings should be done using pybind11 which is already part of the maliput workspace

### To debate
- Extension: Should we provide bindings for the `base` implementation? Providing loader and factory classes for loading a `ObjectQuery` using different implementations could be provided and bindings for the `base` namespace could be avoided.
- Defined: Avoid binding `base` namespace.
- Location: Should this be part of `maliput_py` or at first we could think about it as a package within this repo?
- Defined: Out of maliput_py, within this repo.

### Steps
- [x] Create a `maliput_object_py` package within this repository. https://github.com/ToyotaResearchInstitute/maliput_object/pull/29
- [x] Adds `maliput_object_py` package` to CI. @francocipollone https://github.com/ToyotaResearchInstitute/maliput_object/pull/30
- [x] Create bindings for the `maliput::object::api` namespace. @Voldivh https://github.com/ToyotaResearchInstitute/maliput_object/pull/31
- [ ] Create bindings for the `maliput::object::loader` namespace.
- [ ] Provide methods for getting
- [ ] A bounding region using boundingbox implementation.
- [ ] A object using a boundingbox-based region.
- [ ] A objectquery using a simpleobjectquery implementation.

Start with the existing maliput_object_py package and the completed bindings for the maliput::object::api namespace. Define the remaining scope around bindings for maliput::object::loader and methods for bounding regions, boundingbox-based objects, and simpleobjectquery objects; done means all unchecked items are implemented and covered by the package's CI.

Written by the indexing model from the issue text.