Revert "[inspector] show request method, path, and querystring"

[rudolf]

This reverts commit d61a5a0 from #166565

Summary

Summarize your PR. If it involves visual changes include a screenshot or gif.

Checklist

Delete any items that are not applicable to this PR.

• Any text added follows EUI's writing guidelines, uses sentence case text and includes i18n support
• Documentation was added for features that require explanation or tutorials
• Unit or functional tests were updated or added to match the most common scenarios
• Any UI touched in this PR is usable by keyboard only (learn more about keyboard accessibility)
• Any UI touched in this PR does not create any new axe failures (run axe in browser: FF, Chrome)
• If a plugin configuration key changed, check if it needs to be allowlisted in the cloud and added to the docker list
• This renders correctly on smaller devices using a responsive layout. (You can test this in your browser)
• This was checked for cross-browser compatibility

Risk Matrix

Delete this section if it is not applicable to this PR.

Before closing this PR, invite QA, stakeholders, and other developers to identify risks that should be tested prior to the change/feature release.

When forming the risk matrix, consider some of the following examples and how they may potentially impact the change:

Risk	Probability	Severity	Mitigation/Notes
Multiple Spaces—unexpected behavior in non-default Kibana Space.	Low	High	Integration tests will verify that all features are still supported in non-default Kibana Space and when user switches between spaces.
Multiple nodes—Elasticsearch polling might have race conditions when multiple Kibana nodes are polling for the same tasks.	High	Low	Tasks are idempotent, so executing them multiple times will not result in logical error, but will degrade performance. To test for this case we add plenty of unit tests around this logic and document manual testing procedure.
Code should gracefully handle cases when feature X or plugin Y are disabled.	Medium	High	Unit tests will verify that any feature flag or plugin combination still results in our service operational.
See more potential risk examples

For maintainers

• This was checked for breaking API changes and was labeled appropriately

[elasticmachine]

Pinging @elastic/kibana-core (Team:Core)

[kibana-ci]

💛 Build succeeded, but was flaky

• Buildkite Build
• Commit: 70b6b55

Failed CI Steps

• FTR Configs #14
• FTR Configs #51
• FTR Configs #62

Test Failures

• [job] [logs] FTR Configs #14 / serverless common UI Index Management Create enrich policy can create an enrich policy
• [job] [logs] FTR Configs #51 / serverless observability UI landing page has quickstart badge

Metrics [docs]

Module Count

Fewer modules leads to a faster build time

id	before	after	diff
inspector	57	56	-1

Public APIs missing comments

Total count of every public API that lacks a comment. Target amount is 0. Run node scripts/build_api_docs --plugin [yourplugin] --stats comments for more detailed information.

id	before	after	diff
kibanaUtils	419	417	-2

Async chunks

Total size of all lazy-loaded chunks that will be downloaded as the user navigates the app

id	before	after	diff
inspector	26.4KB	26.2KB	-203.0B

Page load bundle

Size of the bundles that are downloaded on every page load. Target size is below 100kb

id	before	after	diff
data	407.9KB	407.7KB	-205.0B
inspector	22.2KB	21.8KB	-414.0B
total			-619.0B

Unknown metric groups

API count

id	before	after	diff
data	3310	3308	-2
kibanaUtils	612	610	-2
total			-4

History

• 💔 Build #163358 failed e33b378

To update your PR or re-run it, just comment with:
@elasticmachine merge upstream

[delanni]

Admin merging, considering this is a revert, and time sensitive.