CI fails for PRs from forks on extension repo

[rursprung]

it seems that with the new AWS credentials setup introduced by @jandroav CI always fails if PRs come from a fork.

example failure: https://github.com/liquibase/liquibase-opensearch/actions/runs/17205443794/job/48804915473?pr=170

Run aws-actions/configure-aws-credentials@v4
Error: Credentials could not be loaded, please check your action inputs: Could not load credentials from any providers

this step fails:

build-logic/.github/workflows/os-extension-test.yml

Lines 61 to 65 in e9e0c10

	- name: Configure AWS Credentials
	uses: aws-actions/configure-aws-credentials@v4
	with:
	role-to-assume: ${{ secrets.LIQUIBASE_VAULT_OIDC_ROLE_ARN }}
	aws-region: us-east-1

contributions from a fork really should be possible, otherwise you lose out on help from others!

CC @filipelautert

[rursprung]

even on PRs from the same repo the "Attach Artifact to Release" workflow (another than the one reported initially which fails for forks!) fails, see e.g. https://github.com/liquibase/liquibase-opensearch/actions/runs/17205534929/job/48805200583?pr=171