[Heartbeat] Update step name field to use keyword and text

[justinkambic]

What does this PR do?

Adds keyword field to synthetics.step.name.

Why is it important?

We need to be able to bucket based on this field in the exploratory view.

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

• Test locally
• Review code

How to test this PR locally

Run the example synthetics journey from the docs. You should be able to find documents using a query like:

{
  "query": {
    "bool": {
      "filter": [
        {
          "term": {
            "synthetics.step.name.keyword": "hover over products menu"
          }
        }
      ]
    }
  }
}

Related issues

• Closes [Heartbeat] Index synthetics.step.name as keyword as well #28430.

Use cases

Makes it possible to key on synthetics.step.name, which is useful for a number of UI applications when displaying synthetic browser monitoring data in Kibana.

Screenshots

N/A

Logs

N/A

[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 28430/add-keyword-field upstream/28430/add-keyword-field
git merge upstream/master
git push upstream 28430/add-keyword-field

[mergify]

This pull request does not have a backport label. Could you fix it @justinkambic? 🙏
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.

[andrewvc]

LGTM

[elasticmachine]

Pinging @elastic/uptime (Team:Uptime)

[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: 2021-10-14T18:22:45.369+0000

• Duration: 67 min 28 sec

• Commit: 5890805

Test stats 🧪

Test	Results
Failed	0
Passed	3543
Skipped	80
Total	3623

💚 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.

[shahzad31]

Post FF Testing Looks good !!