Feat: Add TAM Instrument with TAM-1, TAM-2 and TAM-3

[rakshityadav1868]

fixes #1213

This PR adds support for the TAM as a new evaluation instrument.

Users can now select TAM-1, TAM-2 or TAM-3 while creating a task, fill version-specific TAM forms, and view the results in a new TAM Analytics section, similar to existing SUS and NASA-TLX workflows.

The implementation includes:
• New TAM form components for all three versions
• Persistent storage of TAM responses with version tagging

This introduces a complete end-to-end TAM flow without affecting existing SUS or NASA-TLX functionality.

[github-actions]

⚠️ PR Description Issues Detected

• Description is too short (minimum 20 characters)

Please update the PR description to address these issues.

[Nirvanjha2004]

Hi @rakshityadav1868 , I pulled your branch locally to test the TAM implementation, but I ran into multiple blocking issues:

1. Build Failure: The build fails immediately because StepperHeader.vue is imported but missing from the files. I had to manually remove that import to get the app to start.
2. Runtime Crash: Once the app is running, attempting to save a TAM response crashes with a FirebaseError: Unsupported field value: undefined. It appears the TAM data model isn't correctly initializing or capturing the answer fields before sending them to Firestore.
   Could you please fix the missing component and debug the data saving logic? The feature currently cannot be tested.

[rakshityadav1868]

I have fixed all issues and updated the PR.

[sonarqubecloud]

Quality Gate failed

Failed conditions
C Reliability Rating on New Code (required ≥ A)

See analysis details on SonarQube Cloud

Catch issues before they fail your Quality Gate with our IDE extension SonarQube for IDE