Mesh objects from db files

### Description of the feature

For the implementation of DPF in PyMAPDL, I have started by enhancing the PyMAPDL mesh object. I would like to use the DPF Mesh_region object as a complement of the dynamic methods we already have.

The issue is it seems I cannot create a mesh object from a DB file. I believe it has to be a DB file because I do *not* want to solve the model.
In MAPDL, when you save the format seems to be `db` always.

In addition, as discussed with @PProfizi, when you try to create a mesh object from a DB file the error is ... obscure.

```py

>>> from ansys.dpf import core as dpf
>>> model = dpf.Model('model_ptyicsrvkq.db')
>>> model.metada.mesh # Raise error
Traceback (most recent call last):
File "", line 1, in
File "c:\users\gayuso\other_projects\pydpf-core\ansys\dpf\core\errors.py", line 136, in wrapper
raise DPFServerException(details)
ansys.dpf.core.errors.DPFServerException: MeshProvider:9<-meshes_provider:10<-Operator(s) (mapdl::db::MeshProvider) does not exists in the registry !
```
[model_ptyicsrvkq.txt](https://github.com/pyansys/pydpf-core/files/9179564/model_ptyicsrvkq.txt)

Attached the DB file as a TXT.

### Steps for implementing the feature

I wish I knew...

### Useful links and references

_No response_

Start by reproducing the failure with dpf.Model using the attached model_ptyicsrvkq.txt DB file, then inspect the metadata.mesh access and the MeshProvider error shown in the issue. Determine the required support for creating a mesh from a MAPDL DB file and define a clear error outcome for unsupported files. Done means DB-backed mesh creation works without solving the model, or the limitation is reported clearly.

Written by the indexing model from the issue text.