Fix macOS package extraction error due to absolute build paths

[vikman90]

Description

This pull request resolves an issue occurring during the extraction of build artifacts on macOS, where the system rejects creating absolute paths such as /Users/runner/.... The error is caused by a mismatch between the build environment (GitHub Actions) and the packaging environment (internal VPN host).

Proposed Changes

• Avoid including the full absolute directory structure in the compressed build artifact.
• Transfer only relevant subdirectories: src, build, and the install directory generated by cmake --install.
• On the packaging host, relocate the install tree instead of re-installing or decompressing into protected system paths.

This change isolates build and install steps cleanly and ensures compatibility between CI and VPN hosts.

Results and Evidence

• The archive now only contains relative paths:
  • wazuh-agent/src
  • wazuh-agent/build
  • wazuh-agent/install
• Decompression and relocation succeed without requiring root or writing to protected locations.
• The packaging scripts correctly consume the relocated install structure.

Status	Workflow	Run
🟢	6_builderpackage_agent-macos	#37

Artifacts Affected

• macOS Wazuh agent installer package (.pkg)
• Intermediate ZIP artifact for ARM64 architecture

Configuration Changes

None required.

Documentation Updates

Not applicable.

Tests Introduced

No new tests introduced.

Installation and uninstallation tests continue to pass and validate the new install directory structure.

Review Checklist

• Code changes reviewed
• Relevant evidence provided
• Tests cover the new functionality
• Configuration changes documented
• Developer documentation reflects the changes
• Meets requirements and/or definition of done
• No unresolved dependencies with other issues

[MarcelKemp]

LGTM.