chore: use relative include path for internal headers

Type of change

• Bug Fix
• Feature

Does this introduce a change in the core logic?

• [Yes]

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

• AWS
• Azure
• GCP
• IBM

Updates description?

Use relative include path when internal header is used in the segysdk to avoid conflict when using the segysdk_public/api.