Build CLI: Configurations on User Level & CI Improvements

[AmmarAbouZor]

This PR closes #2119 This PR closes #2140 This PR closes #2141

It provides a way for the users to configure their environment and preferences in a file in Chipmunk home directory to be loaded and used by the build CLI tool

It Provides fixes improvements in fixes to run CI checks which are described in the linked issues.

The following configuration are provided currently:

• The Shell to run the processes on (Bash, Zsh, Fish...)
• Default UI preference to use with the tool (bars, report, print, immediate)

Roadmap:

• [x] Implement user configurations as singleton with their load method
• [x] Provide an enum to represent the shell running by users with methods to provide command to run process in the selected shell.
• [x] Replace the implementation global commands function with the one from the user configurations.
• [x] Add CLI commands to print the path of the configuration file and dump the default configurations to stdout and to the configuration file.
• [x] Validate given shell before running any further commands.
• [x] Consider preferred UI mode form the configuration.
• [x] Use default values for not defined configurations
• [x] Extend integration tests.
• [x] Extend README.
• [x] Increase tool version.
• [x] Timeout for all spawned tasks to prevent stuck task from running in GitHub actions forever.
• [x] Remove specified targets on test commands in CI checks
• [x] Use cargo to install wasm-pack
• [x] Print error logs to stderr in immediate mode.
• [x] Print info line for skipped jobs in immediate mode.
• [x] Test on Windows.
• [ ] Test on MacOS.

[AmmarAbouZor]

@DmitryAstafyev The default shell will be retrieved from SHELL environment variable. I'll test this PR on Linux and Windows, but could you please test it on MacOS

[AmmarAbouZor]

Test passes on Windows

[AmmarAbouZor]

Timeout has been implemented within CI checks themselves instead of building them inside the CLI tool itself