Refactor tender detail models and UI components for improved clarity and functionality

- Updated the `Lot`, `Organization`, and `OrganizationAddress` models to enhance data mapping for tender details.
- Revised the `TenderData` model to include additional fields reflecting the API response structure.
- Improved UI components across desktop, mobile, and tablet views by commenting out unused sections for future use.
- Added new string constants for lot details in the tender information section.
- Enhanced unit tests to cover new model fields and ensure resilience to partial API payloads.

lib/data/services/model/organization/organization.dart

@@ -6,11 +6,11 @@ import 'package:tm_app/data/services/model/organization/organization_address.dar
 part 'organization.freezed.dart';
 part 'organization.g.dart';
 
-// AI-NOTE (for PR reviewer): Added company_id and a nested address
-// (OrganizationAddress) to surface buyer details on the tender-details page.
-// A dedicated OrganizationAddress type is used instead of the existing
-// `Address` model because the buyer address shape differs (city_name +
-// country_code only) and is unrelated to the user-profile Address.
+// company_id and a nested address (OrganizationAddress) surface buyer details
+// on the tender-details page. A dedicated OrganizationAddress type is used
+// instead of the existing `Address` model because the buyer address shape
+// differs (city_name + country_code only) and is unrelated to the user-profile
+// Address.
 @freezed
 abstract class Organization with _$Organization {
   const factory Organization({