Refactor and Add Component Tests

[Yiling-J]

This PR adding unit tests for the repo/user/space/model/accounting components. Some tests are currently failed and commented out because they were written based on the CSGHub enterprise/cloud version of the code. There are differences between the open-source version (this repository) and the enterprise/cloud version, which is causing these tests to fail.

We are in the process of refactoring the entire project to improve support for different versions, making it easier to develop, test, and build. Since significant changes are expected during this refactoring, the best course of action for now is to comment out the failing tests and revisit them once the refactor is complete.

Other refactors in this PR include:

• Using wire to initialize test components and mocks, as some components have complex dependencies.
• Adding additional linters and fixing some typos.

[starship-github]

🚀 The StarShip CodeReviewer has been triggered with action(s): review, evaluate, describe, linter.

[starship-github]

Linter Issue Report

During the code review, a list issues were found. These issues could affect the code quality, maintainability, and consistency. Below is the detailed Linter issue report:

component/wireset.go

Lint Issue: undefined: TagComponent

• Location: Line 45, Column 16
• Code Context:

  wire.Bind(new(TagComponent), new(*mock_component.MockTagComponent)),

• Actionable Suggestion:
  It appears that TagComponent is referenced but not defined within this file or its imports. Ensure that TagComponent is correctly defined in one of the imported packages or within this file. If it's meant to be part of an external package, verify that the package is imported correctly. If TagComponent is supposed to be defined in this project, you may need to create the appropriate type or interface definition for it. For example:

  type TagComponent interface {
      // Expected methods for TagComponent
  }

  Alternatively, if TagComponent is defined in another file of your project, ensure that its package is correctly imported in wireset.go.

---

Please make the suggested changes to improve the code quality.

[ganisback]

LGTM

[starship-github]

The StarShip CodeReviewer was triggered but terminated because it encountered an issue: litellm.Timeout: APITimeoutError - Request timed out.
error_str: Request timed out.

Tips

CodeReview Commands (invoked as MR or PR comments)

• @codegpt /review to trigger an code review.
• @codegpt /evaluate to trigger code evaluation process.
• @codegpt /describe to regenerate the summary of the MR.
• @codegpt /secscan to scan security vulnerabilities for the MR or the Repository.
• @codegpt /help to get help.

CodeReview Discussion Chat

There are 2 ways to chat with Starship CodeReview:

• Review comments: Directly reply to a review comment made by StarShip.
  Example:
  • @codegpt How to fix this bug?
• Files and specific lines of code (under the "Files changed" tab):
  Tag @codegpt in a new review comment at the desired location with your query.
  Examples:
  • @codegpt generate unit testing code for this code snippet.

Note: Be mindful of the bot's finite context window.
It's strongly recommended to break down tasks such as reading entire modules into smaller chunks.
For a focused discussion, use review comments to chat about specific files and their changes, instead of using the MR/PR comments.

CodeReview Documentation and Community

• Visit our Documentation
  for detailed information on how to use Starship CodeReview.

[SeanHH86]

lgtm

[ganisback]

LGTM

[starship-github]

The StarShip CodeReviewer was triggered but terminated because it encountered an issue: The MR state is not opened.

Tips

CodeReview Commands (invoked as MR or PR comments)

• @codegpt /review to trigger an code review.
• @codegpt /evaluate to trigger code evaluation process.
• @codegpt /describe to regenerate the summary of the MR.
• @codegpt /secscan to scan security vulnerabilities for the MR or the Repository.
• @codegpt /help to get help.

CodeReview Discussion Chat

There are 2 ways to chat with Starship CodeReview:

• Review comments: Directly reply to a review comment made by StarShip.
  Example:
  • @codegpt How to fix this bug?
• Files and specific lines of code (under the "Files changed" tab):
  Tag @codegpt in a new review comment at the desired location with your query.
  Examples:
  • @codegpt generate unit testing code for this code snippet.

Note: Be mindful of the bot's finite context window.
It's strongly recommended to break down tasks such as reading entire modules into smaller chunks.
For a focused discussion, use review comments to chat about specific files and their changes, instead of using the MR/PR comments.

CodeReview Documentation and Community

• Visit our Documentation
  for detailed information on how to use Starship CodeReview.