chore(deps): update dependency @eslint/eslintrc to v3.3.6 (#3719)

Co-authored-by: elastic-renovate-prod[bot] <174716857+elastic-renovate-prod[bot]@users.noreply.github.com>

fix(build): use relative ASSET_PATH for versioned deploy builds (#3715)

Absolute ASSET_PATH derived from BUILDKITE_BRANCH is brittle across
branch/tag naming (tag builds append a date suffix, requiring extra
stripping logic to match upload.sh's deploy directory). A relative
base resolves correctly regardless of the served path, removing that
coupling. Default branch builds (ASSET_PATH unset) are unaffected, so
other products embedding this build with an absolute base keep their
current behavior.

Co-authored-by: Claude Sonnet 5 <noreply@anthropic.com>

fix(build): use relative ASSET_PATH for versioned deploy builds (#3715)…

… (#3716)

Absolute ASSET_PATH derived from BUILDKITE_BRANCH is brittle across
branch/tag naming (tag builds append a date suffix, requiring extra
stripping logic to match upload.sh's deploy directory). A relative
base resolves correctly regardless of the served path, removing that
coupling. Default branch builds (ASSET_PATH unset) are unaffected, so
other products embedding this build with an absolute base keep their
current behavior.


(cherry picked from commit 50ec947)

Co-authored-by: Jorge Sanz <jorge.sanz@elastic.co>
Co-authored-by: Claude Sonnet 5 <noreply@anthropic.com>

fix(build): use relative ASSET_PATH for versioned deploy builds (#3715)…

… (#3718)

Absolute ASSET_PATH derived from BUILDKITE_BRANCH is brittle across
branch/tag naming (tag builds append a date suffix, requiring extra
stripping logic to match upload.sh's deploy directory). A relative
base resolves correctly regardless of the served path, removing that
coupling. Default branch builds (ASSET_PATH unset) are unaffected, so
other products embedding this build with an absolute base keep their
current behavior.


(cherry picked from commit 50ec947)

Co-authored-by: Jorge Sanz <jorge.sanz@elastic.co>
Co-authored-by: Claude Sonnet 5 <noreply@anthropic.com>

fix(build): use relative ASSET_PATH for versioned deploy builds (#3715)…

… (#3717)

Absolute ASSET_PATH derived from BUILDKITE_BRANCH is brittle across
branch/tag naming (tag builds append a date suffix, requiring extra
stripping logic to match upload.sh's deploy directory). A relative
base resolves correctly regardless of the served path, removing that
coupling. Default branch builds (ASSET_PATH unset) are unaffected, so
other products embedding this build with an absolute base keep their
current behavior.


(cherry picked from commit 50ec947)

Co-authored-by: Jorge Sanz <jorge.sanz@elastic.co>
Co-authored-by: Claude Sonnet 5 <noreply@anthropic.com>

chore: bump version to 9.5 (#3385)

Co-authored-by: Claude Sonnet 4.6 <noreply@anthropic.com>

Merge remote-tracking branch 'elastic/master' into v9.4

fix(deps): update elastic eui (#3372)

Co-authored-by: elastic-renovate-prod[bot] <174716857+elastic-renovate-prod[bot]@users.noreply.github.com>

fix(deps): update elastic eui (#3374)

Co-authored-by: elastic-renovate-prod[bot] <174716857+elastic-renovate-prod[bot]@users.noreply.github.com>

chore(deps): update node.js to v24.14.1 (#3379)

Co-authored-by: elastic-renovate-prod[bot] <174716857+elastic-renovate-prod[bot]@users.noreply.github.com>