Allow identity, ensure dimensions is returned, & use pre-commit.ci

[CasperWA]

This PR implements 3 things:

1. Support for aliasing uri as identity in entities.
2. Ensure dimensions is always returned.
3. Use pre-commit.ci

Aliasing uri as identity

In the backend, the entities will still use uri. This is similar to the behaviour of dims/shape, where dims is an alias for shape and shape is what is stored in the backend.

This also means when returning the entity from the service uri (and shape) will be used in place of the aliases.

Ensure dimensions is always returned

Always return dimensions from a call to the service. Even if dimensions is an empty list or dict/object.
In the backend, if dimensions is empty, the key will not be stored for the given document/entity.

Use pre-commit.ci

Set up configuration for pre-commit.ci usage in .pre-commit-config.yaml.
It will run pre-commit for each PR as a CI job.
Hence, the current CI job, which runs pre-commit has been "turned off".

[codecov]

Codecov Report

Attention: Patch coverage is 93.33333% with 2 lines in your changes missing coverage. Please review.

Project coverage is 92.27%. Comparing base (326de73) to head (8ca76a3).
Report is 33 commits behind head on main.

Files with missing lines	Patch %	Lines
entities_service/service/utils.py	92.00%	2 Missing ⚠️

Additional details and impacted files

@@            Coverage Diff             @@
##             main     #103      +/-   ##
==========================================
+ Coverage   92.26%   92.27%   +0.01%     
==========================================
  Files          26       27       +1     
  Lines        1357     1385      +28     
==========================================
+ Hits         1252     1278      +26     
- Misses        105      107       +2     

Flag	Coverage Δ
docker	80.28% <76.66%> (-0.11%)	⬇️
local	91.19% <93.33%> (+0.03%)	⬆️

Flags with carried forward coverage won't be shown. Click here to find out more.

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

[quaat]

I was thinking we could perhaps consolidate the different existing schemas for entities and make a conversion tool in the soft7 package such that we could "upgrade". That way we don't have to implement any version checking in other tools.

[CasperWA]

I was thinking we could perhaps consolidate the different existing schemas for entities and make a conversion tool in the soft7 package such that we could "upgrade". That way we don't have to implement any version checking in other tools.

I fully agree with this sentiment. Indeed, issue #80 reflects part of this thought.