Chore: Add 30-minute timeouts to GitHub Actions workflow jobs

[jaegeral]

Summary

This pull request introduces a consistent 30-minute timeout (timeout-minutes: 30) to various jobs across our GitHub Actions workflows. Previously, these jobs would use the GitHub Actions default timeout of 360 minutes (6 hours).

Changes Made

The timeout-minutes: 30 setting has been applied to the following workflow jobs:

• End-to-End Tests (e2e-tests.yml):
  • PyPi-plaso-stable-opensearch-v1
  • PyPi-plaso-staging-opensearch-v1
  • PyPi-plaso-stable-opensearch-v2
  • PyPi-plaso-staging-opensearch-v2
• Unit Tests (unit-tests.yml):
  • Python (backend tests)
  • VueJS (frontend tests)
• Frontend Builds:
  • build-frontend-ng (in build_frontend-ng.yml)
  • build-frontend-v3 (in build_frontend-v3.yml)

Benefits

• Improved Resource Management: Prevents runaway jobs from consuming excessive runner time by enforcing a 30-minute limit, a significant reduction from the 6-hour default.
• Faster Feedback on Stuck Jobs: If a job hangs or takes unexpectedly long, it will now fail faster, allowing for quicker identification and resolution of underlying issues.
• Consistency: Standardizes job execution time limits across different testing and build workflows.

This change enhances the reliability and efficiency of our CI pipeline.

closes #3352