CI release fails due to new example

[PProfizi]

Before submitting the issue

• I have checked for Compatibility issues
• I have searched among the existing issues
• I am using a Python virtual environment

Description of the bug

The development CI tests pydpf-core against the development version of the DPF server.
The release CI however, tests whether pydpf-core can be released at any time, and tests against the last released DPF server.

A problem arises when an example (or a test), using new operators available only in the dev DPF server, is merged into the master branch.
The release CI understandably fails, since the example is not flagged in any manner as requiring a minimal DPF server version.

To prevent us from having to filter PRs and make them wait, we need a way to flag examples with a minimal required DPF Server version, and to add the logic in the CI to not run those if the server version is too low.

This would also increase visibility for each example on what version the feature starts being available with.
A note, or a warning, should be added to new (every?) examples.

Steps To Reproduce

https://github.com/pyansys/pydpf-core/actions/runs/4036910763/jobs/6939844493#step:8:2350

Which Operating System are you using?

Windows

Which DPF/Ansys version are you using?

DPF Server as standalone

Which Python version are you using?

3.7

Installed packages

https://github.com/pyansys/pydpf-core/actions/runs/4036910763/jobs/6939844493#step:7:21

[PProfizi]

@cbellot000 @anslpa @rafacanton any opinion on this?

[rafacanton]

To prevent us from having to filter PRs and make them wait, we need a way to flag examples with a minimal required DPF Server version, and to add the logic in the CI to not run those if the server version is too low.

I think we already do something similar: look at line 7. We would need similar conftests for individual server versions, right?

[PProfizi]

To prevent us from having to filter PRs and make them wait, we need a way to flag examples with a minimal required DPF Server version, and to add the logic in the CI to not run those if the server version is too low.

I think we already do something similar: look at line 7. We would need similar conftests for individual server versions, right?

Yes, that is what we do for tests. For examples however, this logic does not exist yet, and I think we could find a way to make this transparent for the user (aka not putting ifs in the example's code). I am thinking of adding a Note mentioning a minimal version, and then the script running the examples would parse this note if it exists, and skip the example if necessary.
This way the note prints-out nicely and the user is informed, but no code is added to the example.
It would be both here and here (due to Sphinx gallery).

See here for available note types.