[CVE-2022-33987][2.x]Re-upgrade geckodriver to 3.0.2

[ananzh]

Description

geckodriver - only used in running functional tests. It got bumped to 11.8.5 on 2022-06-02.

geckodriver has been bumped to 3.0.2 before and backported to 2.x PR: #2397

However, due to this PR:
#2409 geckodriver is set back to 3.0.1. Therefore, we will reset it to 3.0.2.

Issues Resolved

#1764

Check List

• All tests pass
  • yarn test:jest
  • yarn test:jest_integration
  • yarn test:ftr
• New functionality includes testing.
• New functionality has been documented.
• Update CHANGELOG.md
• Commits are signed per the DCO using --signoff

[joshuarrrr]

@ananzh It looks like we also need this change in main. Why not PR it there first and then backport?

It is already in main. It is fixed before. Then this backport PR reverted the change.

[opensearch-trigger-bot]

The backport to 2.4 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 working tree
git worktree add .worktrees/backport-2.4 2.4
# Navigate to the new working tree
cd .worktrees/backport-2.4
# Create a new branch
git switch --create backport/backport-2709-to-2.4
# Cherry-pick the merged commit of this pull request and resolve the conflicts
git cherry-pick -x --mainline 1 107a400d2df846a3b73e336c4072afb6de53813b
# Push it to GitHub
git push --set-upstream origin backport/backport-2709-to-2.4
# Go back to the original working tree
cd ../..
# Delete the working tree
git worktree remove .worktrees/backport-2.4

Then, create a pull request where the base branch is 2.4 and the compare/head branch is backport/backport-2709-to-2.4.

[ananzh]

To make package consistency, this PR is superseded by this later one: #2772