NOISSUE - Enable WASM Support and FileSystem Support

[rodneyosodo]

What type of PR is this?

This PR is a feature because it adds support of running wasm algorithms and also adds support for using filesystem to store results for the different algorithms

What does this do?

This pull request introduces support for WebAssembly (Wasm) as a new algorithm type, refactors algorithm creation functions, enhances error handling and logging, updates the CLI for result file path specification, changes the agent build configuration, and updates the Protobuf compiler version in the CI workflow.

• New Features

  • Introduced support for WebAssembly (Wasm) algorithms, expanding the algorithm capabilities.
  • Added a feature to zip the results directory, enhancing result management.

• Improvements

  • Enhanced error handling for algorithm execution and result processing.
  • Refactored the algorithm creation functions to use a more descriptive name NewAlgorithm.

• Configuration Changes

  • I updated the configuration for the WasmEdge package and related build options in the Linux setup.

• CI:

  • Updated the Protobuf compiler version in the CI workflow.

Which issue(s) does this PR fix/relate to?

No issue

Have you included tests for your changes?

Tested manually for binary and wasm targets for https://github.com/ultravioletrs/ai/tree/main/burn-algorithms

Did you document any new/modified feature?

To be updated on https://github.com/ultravioletrs/cocos-docs

Notes

[SammyOina]

also add a wasm example for the lin reg example, in the test directory

[SammyOina]

datasets should be stored in datatsets directory and results in results dir

[SammyOina]

datasets should be stored in datatsets directory and results in results dir

also modify the lin_reg example here