Standardize and clean up workflow naming conventions for TinyTorch and analysis

[profvjreddi]

Currently, our repository contains multiple workflow files that support both TinyTorch and the analysis part. The workflow names are inconsistent and may cause confusion when expanding or maintaining CI/CD operations. We should clean up and standardize the naming conventions of all workflows to:

• Clearly distinguish between TinyTorch workflows and analysis workflows.
• Make future maintenance and onboarding easier.
• Avoid ambiguity for contributors and reviewers.

Tasks:

• List all workflow files and their purposes.
• Propose and implement a clear, consistent naming scheme for CI workflows related to TinyTorch and analysis.
• Update documentation and workflow references if necessary.

This cleanup will help streamline development processes and reduce errors due to misidentified workflows.

[GabrielAmazonas]

Hi @profvjreddi - I'd like to work on this and share a Pull Request with the selected approach and tooling used - thanks for the opportunity!

[profvjreddi]

Hi @GabrielAmazonas -- any contributions are certainly welcome, but I just realized that since this issue was created, I've cleaned the code up quite a bit and fixed many bugs and issues. Nonetheless, if you spot something, feel free to let me know. This is an open-source project because the intent is for others to contribute. Thank you for volunteering!