Move the Fluent API tests to run with 24.1 Fluent version

[mkundu1]

This will fix 23.1 nightly failure - https://github.com/ansys/pyfluent/actions/runs/5676374753/job/15383014718#step:24:1229

[seanpearsonuk]

FOR SEPARATE CONSIDERATION For a directory like test_solvermode, where we are purely exercising a Fluent API, the testing of released Fluent versions can be considered complete, and anyway any issues cannot be resolved any more. Therefore, I would propose that this directory is only applicable to the latest version - the current unreleased version under development. If we can associate a whole directory with a release version without additional need for marking individual tests, that would be ideal. Other tests, that aren't purely concerned with API testing should try to minimise and simplify their API use and try to use stable parts of APIs.

[mkundu1]

FOR SEPARATE CONSIDERATION For a directory like test_solvermode, where we are purely exercising a Fluent API, the testing of released Fluent versions can be considered complete, and anyway any issues cannot be resolved any more. Therefore, I would propose that this directory is only applicable to the latest version - the current unreleased version under development. If we can associate a whole directory with a release version without additional need for marking individual tests, that would be ideal. Other tests, that aren't purely concerned with API testing should try to minimise and simplify their API use and try to use stable parts of APIs.

Agree, these tests should test the Fluent API under development as that is the only thing which may fail these tests. We already have documentation examples and pyfluent-examples repo to demonstrate Fluent API usage of the released Fluent version. I'll mark these tests with 24.1 which will also reduce the test running time.

[seanpearsonuk]

FOR SEPARATE CONSIDERATION For a directory like test_solvermode, where we are purely exercising a Fluent API, the testing of released Fluent versions can be considered complete, and anyway any issues cannot be resolved any more. Therefore, I would propose that this directory is only applicable to the latest version - the current unreleased version under development. If we can associate a whole directory with a release version without additional need for marking individual tests, that would be ideal. Other tests, that aren't purely concerned with API testing should try to minimise and simplify their API use and try to use stable parts of APIs.

Agree, these tests should test the Fluent API under development as that is the only thing which may fail these tests. We already have documentation examples and pyfluent-examples repo to demonstrate Fluent API usage of the released Fluent version. I'll mark these tests with 24.1 which will also reduce the test running time.

Thanks a lot @mkundu1.

@cj-hodgson @millerj97 letting you know what we're up to here