Release v3 compatible ASTE version

[davidscn]

Main changes of this PR

TODO: add more detailed changes.

Author's checklist

• [x] I used the pre-commit hook and used pre-commit run --all to apply all available hooks.
• [x] I added a test to cover the proposed changes in our test suite.
• [x] I updated the documentation in docs/README.md.
• [x] I updated potential breaking changes in the tutorial precice/tutorials/aste-turbine.

[davidscn]

Some status update and summary:

The CI is currently failing and I can reproduce this behavior on my local machine. The issue occurs when using precice-aste-evaluate and storing a mesh in VTU file format and trying to read it afterwards, using any of the VTK facilities (python or C++).

The error message:

 (   0.373s) [        9D6DFE00]       vtkXMLParser.cxx:375    ERR| vtkXMLDataParser (0x5639d4af14c0): Error parsing XML in stream at line 24, column 19, byte index 1649: not well-formed (invalid token)
 (   0.373s) [        9D6DFE00]       vtkXMLReader.cxx:521    ERR| vtkXMLUnstructuredGridReader (0x5639d4bb6080): Error parsing input file.  ReadXMLInformation aborting.
 (   0.373s) [        9D6DFE00]       vtkExecutive.cxx:752    ERR| vtkCompositeDataPipeline (0x5639d4b00ed0): Algorithm vtkXMLUnstructuredGridReader(0x5639d4bb6080) returned failure for request: vtkInformation (0x5639d4bff260)
  Debug: Off
  Modified Time: 153
  Reference Count: 1
  Registered Events: (none)
  Request: REQUEST_INFORMATION
  ALGORITHM_AFTER_FORWARD: 1
  FORWARD_DIRECTION: 0

The curious thing: Yesterday (before I executed my apt upgrade) I was not able to reproduce the issue and everything was ok.

After some digging, my best guess is the upgrade of libexpat1-dev (xml parser). I found a recent issue in the arch package and it is also discussed in the paraview discourse. We can also see in our CI, that the tests passed on develop four weeks before, whereas now they are failing without obious reasons.

EDIT: Although the arch discussion is referring to version 2.6 and in ubuntu we are talking about an update from 2.4.7-1ubuntu0.2 to 2.4.7-1ubuntu0.3, running apt changelog libexpat1 points to the same problematic changes as discussed in the corresponding libexpat1 issues where the discussion bisects to (this changes backported to the ubuntu package 2.4.7-1ubuntu0.3).