Refactor Tender Management to Introduce Notice Entity and Repository

- Replaced the tender repository with a new notice repository, encapsulating notice-related data access methods.
- Introduced the Notice entity to represent tender/contract notices, including relevant fields and methods for managing notice data.
- Updated the TED scraper to utilize the new notice repository for creating and managing notices, enhancing the integration with the tender management system.
- Implemented Ollama SDK initialization in the web bootstrap process, allowing for improved AI interactions.
- Enhanced the tender service to include Ollama SDK for additional functionality, ensuring a more robust service layer.

internal/tender/service.go

@@ -6,6 +6,7 @@ import (
 	"time"
 	"tm/internal/company"
 	"tm/pkg/logger"
+	"tm/pkg/ollama"
 	"tm/pkg/response"
 )
 
@@ -27,14 +28,16 @@ type Service interface {
 type tenderService struct {
 	repository     TenderRepository
 	companyService company.Service
+	ollamaSDK      ollama.SDK
 	logger         logger.Logger
 }
 
 // NewService creates a new tender service
-func NewService(repository TenderRepository, companyService company.Service, logger logger.Logger) Service {
+func NewService(repository TenderRepository, companyService company.Service, ollamaSDK ollama.SDK, logger logger.Logger) Service {
 	return &tenderService{
 		repository:     repository,
 		companyService: companyService,
+		ollamaSDK:      ollamaSDK,
 		logger:         logger,
 	}
 }