fix: File Metadata Service Api header change

Type of change

• Bug Fix
• Feature

Does this introduce a change in the core logic?

• No
• Yes

Does this introduce a change in the cloud provider implementation, if so which cloud?

• AWS
• Azure
• GCP
• IBM

Does this follow conventional commits spec?

• No
• Yes

Have you set the Milestone?

• No
• Yes

Have you set the no-detached-pipeline label?

• No
• Yes

Updates description?

Add default api key header for workaround. Need further cleanup once new version of segysdk is ready