readd session token to s3 credentials

[farodin91]

What this PR does:
Support was removed in #3006

Which issue(s) this PR fixes:
Fixes #

Checklist

• Tests updated
• Documentation added
• CHANGELOG.md updated - the order of entries should be [CHANGE], [FEATURE], [ENHANCEMENT], [BUGFIX]

[joe-elliott]

Thanks for catching and fixing this. Can you add a changelog entry?

[farodin91]

changelog added

[joe-elliott]

Looks good! Thanks for the fix. Do you need this backported to use 2.3?

cc @mapno

[farodin91]

@joe-elliott Would be nice.

[github-actions]

The backport to release-v2.3 failed:

The process '/usr/bin/git' failed with exit code 1

To backport manually, run these commands in your terminal:

# Fetch latest updates from GitHub
git fetch
# Create a new branch
git switch --create backport-3144-to-release-v2.3 origin/release-v2.3
# Cherry-pick the merged commit of this pull request and resolve the conflicts
git cherry-pick -x 3008ee5c610129fb16bce408fa17b39c26cf5b5f

When the conflicts are resolved, stage and commit the changes:

git add . && git cherry-pick --continue

If you have the GitHub CLI installed:

# Push the branch to GitHub:
git push --set-upstream origin backport-3144-to-release-v2.3
# Create the PR body template
PR_BODY=$(gh pr view 3144 --json body --template 'Backport 3008ee5c610129fb16bce408fa17b39c26cf5b5f from #3144{{ "\n\n---\n\n" }}{{ index . "body" }}')
# Create the PR on GitHub
echo "${PR_BODY}" | gh pr create --title "[release-v2.3] readd session token to s3 credentials" --body-file - --label "type/bug" --label "backport" --base release-v2.3 --milestone release-v2.3 --web

Or, if you don't have the GitHub CLI installed (we recommend you install it!):

# Push the branch to GitHub:
git push --set-upstream origin backport-3144-to-release-v2.3

# Create a pull request where the `base` branch is `release-v2.3` and the `compare`/`head` branch is `backport-3144-to-release-v2.3`.

# Remove the local backport branch
git switch main
git branch -D backport-3144-to-release-v2.3