refactor(file-manager): update FileManagerServicePath with new controller endpoints

Summary

Updates FileManagerServicePath to align with the current FileManager microservice controller architecture.

Why

The existing FileManagerServicePath contained outdated URL patterns that no longer matched the actual controller endpoints. This refactor ensures consistency between URL builders and controller mappings.

Changes

Updated Base Paths

Constant	Path
AGENT_ATTACHMENTS_BASE	/api/file-manager/agent/attachments
AGENT_DOCUMENTS_BASE	/api/file-manager/agent/documents
AGENT_KNOWLEDGE_BASE_BASE	/api/file-manager/agent/knowledge-base
AGENT_WORKFLOW_TEMPLATES_BASE	/api/file-manager/agent/workflow-templates

Renamed/Updated Methods

Old Method	New Method
buildUploadAgentMessageAttachmentsUrl	buildUploadAgentAttachmentsUrl
buildGetAgentMessageAttachmentsUrl	buildGetAgentAttachmentsMetadataUrl
buildUploadSpecificAgentKnowledgeDocumentsUrl	buildUploadAgentDocumentsUrl
buildGetMainN8NWorkflowTemplateForAgentFamilyUrl	buildGetMainWorkflowTemplateMetadataUrl

Added Methods

• buildGetAgentAttachmentsContentUrl
• buildGetAgentDocumentsContentUrl
• buildGetGeneralKnowledgeBaseContentUrl
• buildGetSpecificKnowledgeBaseContentUrl
• buildUploadSubWorkflowTemplatesUrl
• buildGetSubWorkflowTemplatesMetadataUrl
• buildGetSubWorkflowTemplatesContentUrl
• buildDownloadMainWorkflowTemplateUrl

Removed Methods

• buildUploadGeneralAgentFamiliesKBUrl (replaced)
• buildUploadSpecificAgentFamilyKBUrl (replaced)
• buildGetMainN8NWorkflowTemplateContentUrl (consolidated)

Breaking Changes

⚠️ Method signatures and paths have changed. Update all usages in dependent services.

Testing

• Verify all URL builders match controller endpoints
• Update dependent service calls