Change kibana api paths used in container command

[michel-laterman]

What does this PR do?

Change the API paths used by the container command to reflect the updated paths.

Why is it important?

Old paths are deprecated.

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.

Related issues

• Closes Accommodate enrollment-api-keys API change in kibana fleet API #111

[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-03-24T21:07:35.765+0000

• Duration: 16 min 26 sec

🤖 GitHub comments

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

• /test : Re-trigger the build.

• /package : Generate the packages.

• run integration tests : Run the Elastic Agent Integration tests.

• run end-to-end tests : Generate the packages and run the E2E Tests.

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

[ph]

LGTM, Changes are already in Kibana?

[jlind23]

@ph was done there elastic/kibana#119494 by @juliaElastic at least a release ago.