feat: Upload/Download across all API

[hpohekar]

Closes - #2206 and #2195

For cloud platform like the Ansys Lab we need to upload file (case/data/mesh) to server to be able to read it in commands like read_case/ReadCase or read_mesh/ReadMesh and we need to download file from the server after executing commands like write_case/WriteCase or write_mesh/WriteMesh etc.

Right now we have <session>.upload() and <session>.download() methods to upload/download files explicitly but we want to handle this internally.

Therefore to achieve this we have added filePurpose/filepurpose attribute to distinguish between input/output file types. Based on the file purpose we are generating settings classes by adding mixin class to the bases of existing file classes.

So if file purpose is input then we will upload the file and if it is output then we will download it.

We have integrated remote_file_handler in both settings and datamodel __call__ methods to achieve this capability seamlessly.

We have added a TransferRequestRecorder class as a mock file service class to replicate Ansys Lab scenario locally.

[raph-luc]

We are unable to test it in the Ansys Lab as it does not support 24R2 yet.

@hpohekar Right, can we mock/test the implementation in another way that does not rely on Ansys Lab? Otherwise we will indeed need to wait to properly support PyPIM/Ansys Lab.

[hpohekar]

We are unable to test it in the Ansys Lab as it does not support 24R2 yet.

@hpohekar Right, can we mock/test the implementation in another way that does not rely on Ansys Lab? Otherwise we will indeed need to wait to properly support PyPIM/Ansys Lab.

@raph-luc can we mock/test the implementation in another way that does not rely on Ansys Lab? - Yes, I am working on it.