Optimize Pre-Commit Husky Hooks to Use Pre-Push for Build and Test Commands

**Issue Description:**
Currently, our project's pre-commit hooks, configured using Husky, execute build and test commands before each commit. While this approach aims to ensure code quality and prevent faulty commits, it may unintentionally encourage contributors to make bulkier commits, resulting in more challenging code review and maintenance processes. This GitHub issue proposes modifying the Husky configuration to utilize the pre-push hook instead, allowing for a more controlled and streamlined commit workflow.

**Benefits of Shifting to Pre-Push Hook:**

1. **Focused and Granular Commits**: By moving the build and test commands to the pre-push hook, contributors are encouraged to make smaller, focused commits. This shift promotes a more granular approach to code changes, making it easier to review, understand, and manage individual commits. With concise commits, our team can more effectively track changes, pinpoint potential issues, and provide constructive feedback, leading to faster iteration and higher code quality.

2. **Improved Code Review Process**: Bulky commits can make code review more challenging, as it becomes harder to isolate specific changes and understand their impact on the codebase. By utilizing the pre-push hook, contributors have the opportunity to review and revise their changes before pushing them to the shared repository. This proactive step allows for more thorough self-review, resulting in more polished and coherent commits, which, in turn, simplifies the code review process and reduces the burden on reviewers.

3. **Reduced Overhead for Failed Commits**: In the current setup, if the build or test commands fail during the pre-commit hook, the commit itself is prevented. This may lead to frustration for contributors who need to fix unrelated issues before being able to commit their intended changes. By leveraging the pre-push hook, failed build or test commands don't hinder the commit itself, allowing contributors to focus solely on resolving the issues at hand without being burdened by unrelated concerns. This streamlined workflow saves time and improves the developer experience.

4. **Better Integration with Continuous Integration (CI) Pipelines**: Shifting the build and test commands to the pre-push hook ensures a consistent testing environment between local development and the CI pipelines. With the pre-push hook triggering the build and test processes, the local environment closely aligns with the CI environment, reducing the chances of unexpected failures or discrepancies between the two. This alignment facilitates smoother integration with our CI pipelines and provides a more accurate representation of the final build state.

5. **Flexible Testing Strategies**: The pre-push hook allows contributors to choose the appropriate testing strategy for their changes. While the pre-commit hook enforces testing before every commit, it may not be suitable for every development workflow or context. By transitioning to the pre-push hook, contributors can decide whether to run full test suites, specific test subsets, or even skip tests in certain situations, depending on the nature and scope of their changes. This flexibility strikes a balance between thorough testing and development efficiency.

6. **Encourages Continuous Integration and Frequent Pushes**: By separating the build and test steps from the commit process, the pre-push hook encourages contributors to push their changes more frequently. Frequent pushes promote continuous integration and collaboration, ensuring that conflicts are addressed promptly and enabling faster feedback loops among team members. This proactive approach helps minimize merge conflicts, facilitates early bug detection, and creates a more agile and collaborative development environment.

7. **Community-Driven Best Practices**: Shifting to the pre-push hook aligns with best practices and recommendations from the wider developer community. Many successful projects and organizations advocate for a pre-push approach to testing and code quality, emphasizing the benefits of focused commits and efficient code reviews. By adopting this approach, we align ourselves with industry-standard practices, enabling easier collaboration with external contributors and potential open-source initiatives.

Conclusion:
Transitioning from the pre-commit hook to the pre-push hook for executing build and test commands offers several advantages, including focused and granular commits, improved code review processes, reduced overhead for failed commits, better integration with CI pipelines, flexible testing strategies, encouragement of continuous integration, and adherence to community-driven best practices. By implementing this change, we enhance the commit workflow, fostering a more streamlined and efficient development process for our audio editing application.