create activity endpoint returning pull requests with bad practices(#…

[iam-flo]

#199

Motivation

This PR aims to address the challenge of improving the quality of pull request descriptions, particularly for novice software engineers. By developing a system that detects and visualizes bad practices in PR descriptions, we aim to provide actionable insights that enhance understanding and foster better documentation habits.

Description

This PR implements two key components of the system:
Activity Dashboard: A visual interface to display detected bad practices alongside the associated pull requests. This helps users quickly identify areas for improvement.
Bad Practice Rule Page: A configurable interface to define and manage workspace-specific rules for detecting common issues in PR descriptions.
These features form the foundation for the larger system that leverages an LLM for bad practice detection, creating a dynamic and scalable solution.

Testing Instructions

Start both server and client.
Navigate to http://localhost:4200/activities/iam-flo and test activity dashboard
Navigate to http://localhost:4200/workspace and to rules page and test it

Screenshots (if applicable)

Include screenshots here showcasing the Activity Dashboard and Rule Page interfaces if available.

General

• PR title is clear and descriptive
• PR description explains the purpose and changes
• Code follows project coding standards
• Self-review of the code has been done
• Changes have been tested locally
• Screenshots have been attached (if applicable)
• Documentation has been updated (if applicable)

Client (if applicable)

• UI changes look good on all screen sizes and browsers
• No console errors or warnings
• User experience and accessibility have been tested
• Added Storybook stories for new components
• Components follow design system guidelines (if applicable)

Server (if applicable)

• Code is performant and follows best practices
• No security vulnerabilities introduced
• Proper error handling has been implemented
• Added tests for new functionality
• Changes have been tested in different environments (if applicable)