Implement CI/CD Pipeline for Automated Testing and Deployment

## 📚 Overview

Implement a CI/CD pipeline for the escrownet-dapp project to streamline the development workflow by automating testing, building, and deployment. This feature ensures that code quality is maintained and releases are consistent, reducing the likelihood of manual errors.

## 🔍 Background

- The project uses [npm](https://docs.npmjs.com/) for dependency management and scripts
- Automated pipelines help verify that new code changes do not introduce regressions or break existing functionality.

## 🛠️ Requirements

2. **Building the Frontend:**
- Integrate build steps as defined in the project scripts to compile the frontend code.

3. **Deployment:**
- Automate the deployment process for the dApp once the testing and building phases pass successfully.

4. **CI/CD Tool Integration:**
- The implementation should be configurable for the chosen CI/CD tool (e.g., GitHub Actions, GitLab CI, etc.).

5. **Error Handling & Notifications:**
- Implement error handling to catch failing tests or build errors.
- Optionally, set up notifications to alert maintainers on pipeline failures.

## ⚙️ Technical Considerations

- Pipeline triggers should include branch pushes and pull requests to ensure code quality before merging.

## ✅ Definition of Done

- The CI/CD pipeline automatically builds, and deploys the frontend on designated branches.
- Proper error handling and notifications for pipeline failures are in place.
- Documentation is updated to include instructions on how to maintain and troubleshoot the CI/CD pipeline.

Let's make our development process smoother and more reliable! 🚀