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.

ted/service.go

@@ -5,7 +5,7 @@ import (
 	"strconv"
 	"strings"
 	"time"
-	"tm/internal/tender"
+	"tm/internal/notice"
 )
 
 // parseDate parses various date formats used in TED XML
@@ -146,7 +146,7 @@ func GenerateTenderURL(noticePublicationID string) string {
 
 // generateTenderID generates a unique tender ID using the format:
 // {Source}{BUYER_CODE}{TED_CODE}{DATE}{LOCATION_CODE}
-func GenerateTenderID(t *tender.Tender) string {
+func GenerateTenderID(t *notice.Notice) string {
 	var parts []string
 
 	// Source (TED)