x-pack/filebeat/input/cel: mark as GA

[efd6]

What does this PR do?

Marks the CEL input as GA.

Why is it important?

Milestone plan item.

Checklist

• My code follows the style guidelines of this project
• I have commented my code, particularly in hard-to-understand areas
• I have made corresponding changes to the documentation
• I have made corresponding change to the default configuration files
• I have added tests that prove my fix is effective or that my feature works
• I have added an entry in CHANGELOG.next.asciidoc or CHANGELOG-developer.next.asciidoc.

Author's Checklist

• [ ]

How to test this PR locally

Related issues

• Depends x-pack/filebeat/input/cel: provide XML decoding functionality #35372

Use cases

Screenshots

Logs

[elasticmachine]

💚 Build Succeeded

the below badges are clickable and redirect to their specific view in the CI or DOCS

Expand to view the summary

Build stats

• Start Time: 2023-05-31T10:44:04.647+0000

• Duration: 75 min 12 sec

Test stats 🧪

Test	Results
Failed	0
Passed	2922
Skipped	175
Total	3097

💚 Flaky test report

Tests succeeded.

🤖 GitHub comments

Expand to view the GitHub comments

To re-run your PR in the CI, just comment with:

• /test : Re-trigger the build.

• /package : Generate the packages and run the E2E tests.

• /beats-tester : Run the installation tests with beats-tester.

• run elasticsearch-ci/docs : Re-trigger the docs validation. (use unformatted text in the comment!)

[elasticmachine]

Pinging @elastic/security-external-integrations (Team:Security-External Integrations)

[taylor-swanson]

LGTM, just need to make the linter happy.

[efd6]

The linter cannot be made happy here; it is incorrect, and worse, the specific linter (typecheck) should not exist since it is just repeating work done by go tool compile. That is, if the linter were correct the compilation would fail.

The complaint here is that rest is not used, but clearly is in the case body in the switch at the bottom of this snippet.

	key, rest, more := strings.Cut(path, ".")
	v, ok := m[key]
	if !ok {
		return
	}
	if !more {
		fn(m, key)
		return
	}
	switch v := v.(type) {
	case mapstr.M:
		walkMap(v, rest, fn)

Locally, golangci-lint does not complain about this, but the action does. I believe that this is related to golangci/golangci-lint-action#624 which has gained no traction. golangci-lint does not allow this redundant and broken linter to be turned off.