[Filebeat] Add URL Encode template function for httpjson input

[legoguy1000]

What does this PR do?

Add URL Encode tempalte function for httpjson input

Why is it important?

When manually constructing the url.value if there are values that need to be URL encoded.

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

• Relates [Atlassian JIRA & Confluence] Add support for Atlassian Cloud integrations#2715

Use cases

Screenshots

Logs

[mergify]

This pull request does not have a backport label. Could you fix it @legoguy1000? 🙏
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 7./d branch. /d is the digit

NOTE: backport-skip has been added to this pull request.

[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: 2022-04-05T22:34:14.794+0000

• Duration: 69 min 53 sec

Test stats 🧪

Test	Results
Failed	0
Passed	2062
Skipped	159
Total	2221

💚 Flaky test report

Tests succeeded.

🤖 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)

[efd6]

/test

[legoguy1000]

How should I resolve the linting issues? especially the one about unsecure import for sha1 hash?

[andrewkroh]

The existing linter issues are being addressed in #31008. So once that is merged you can merge that in. It uses a //nolint comment to address the cryto/sha warning.

[legoguy1000]

Ok, that's what I was going to add 😁

[mergify]

This pull request is now in conflicts. Could you fix it? 🙏
To fixup this pull request, you can check out it locally. See documentation: https://help.github.com/articles/checking-out-pull-requests-locally/

git fetch upstream
git checkout -b httpjson-url-encode upstream/httpjson-url-encode
git merge upstream/main
git push upstream httpjson-url-encode

[efd6]

/test

[mergify]

This pull request is now in conflicts. Could you fix it? 🙏
To fixup this pull request, you can check out it locally. See documentation: https://help.github.com/articles/checking-out-pull-requests-locally/

git fetch upstream
git checkout -b httpjson-url-encode upstream/httpjson-url-encode
git merge upstream/main
git push upstream httpjson-url-encode

[andrewkroh]

/test

[andrewkroh]

LGTM

[legoguy1000]

@andrewkroh was this ever backported to 8.3?

[andrewkroh]

The 8.3 branch has not been created yet. It will be created from main so there is not backport required.