fix: use latest beats for agent v2

[olegsu]

What does this PR do?
In the agent v2 pr we used to replace github.com/elastic/beats/v7 with a module that supports v2.
The CI step in the main branch failed on the licensing step.
When this PR will be merged we can remove the replace

Related tasks:

• Merge feature arch v2 beats#33630
• https://github.com/elastic/security-team/issues/4792

[mergify]

This pull request does not have a backport label. Could you fix it @olegsu? 🙏
To fixup this pull request, you need to add the backport labels for the needed
branches, such as:

• backport-v./d./d./d is the label to automatically backport to the 8./d branch. /d is the digit
  NOTE: backport-skip has been added to this pull request.

[eyalkraft]

Sanity test required

[github-actions]

Cloudbeat CI 🤖

Allure Report: http://csp-allure-reports.s3.amazonaws.com/allure_reports/cloudbeat/prs/508/index.html

[olegsu]

The latest version in pkg.go.dev is not updated.
So to make sure we are running the module on the latest commit in run from the beats repo

git --no-pager show --quiet --abbrev=12   --format="%h"

After that go get -v github.com/elastic/beats/v7@2e61bb8369f1 and go mod tidy
@cmacknz This might cause issues for other clients that use this package

[yashtewari]

Looks good!