core: DB model and CRUD functionality for strengths

[pingSubhajit]

This issue focuses on establishing the database model and defining the CRUD operations (Create, Read, Update, Delete) for strengths within the application. This will allow users to manage their strengths effectively.

Success Criteria:

• A database model for strengths is defined, including the necessary fields to store strength information.
• CRUD operations for strengths are implemented, allowing users to create, read, update, and delete their strength entries.

Acceptance Criteria:

• Database Model:
  • Name: (required) The name of the strength.
  • UserId: (required) Foreign key referencing the user who owns the strength.
• CRUD Operations:
  • Create: Allows users to create new strength entries, providing the strength name.
  • Read: Retrieves a list of strengths for a specific user.
  • Update: Allows users to modify existing strength entries, updating the strength name.
  • Delete: Enables users to remove strength entries from their profile.
• Data Validation:
  • Validate user input to ensure data integrity and prevent invalid or malicious entries.
  • Error handling is implemented to handle invalid or missing data gracefully.
• Security:
  • Implement appropriate security measures to protect strength data from unauthorized access.
  • Ensure that users can only access and modify their own strength entries.

Additional Notes:

• Implement appropriate authorization and authentication mechanisms to control user access to strength data.
• Document the database model and CRUD operations for future development and maintenance.

This implementation will lay the foundation for managing strength data within the application, providing users with a robust system for creating, updating, and deleting their strength entries.