feat: 🎸 add ability to disable URL encoding in URL Drilldown

[streamich]

Summary

Adds ability to not encode URL in URL Drilldown.

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)
• This renders correctly on smaller devices using a responsive layout. (You can test this in your browser)
• This was checked for cross-browser compatibility

For maintainers

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

[kibanamachine]

💚 Build Succeeded

• continuous-integration/kibana-ci/pull-request
• Commit: 5a415a0

Metrics [docs]

Distributable file count

id	before	after	diff
default	-	42777	+42777

Page load bundle

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

id	before	after	diff
uiActionsEnhanced	304.4KB	305.2KB	+866.0B
urlDrilldown	13.9KB	14.0KB	+116.0B
total			+982.0B

Unknown metric groups

@kbn/ui-shared-deps asset size

id	before	after	diff
css	-	650.1KB	⚠️ +650.1KB
kbn-ui-shared-deps.@elastic.js	-	2.4MB	⚠️ +2.4MB
kbn-ui-shared-deps.js	-	4.8MB	⚠️ +4.8MB
total			⚠️ +7.9MB

History

• 💚 Build #87372 succeeded 2d5f000

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

[streamich]

• design with "Advanced settings"
  • extra explanations text next to checkboxes
• encode helpers, 2 of them (+ and %20) src/plugins/kibana_utils/common/url/encode_uri_query.ts
• add usage examples to public docs, which have full examples of Handlebars usage

[mdefazio]

I gave this a bit more thought and here is another option. I have the advanced settings (Maybe 'Additional options' is less scary?) below the 'Open in new tab' option since it seemed to make sense that we expose options first and then have additional hidden options below.

[elastic-jb]

@streamich This looks good to me. I would like to bring in one more thought after talking through it with @mdefazio . Nearly every time I am turning on "open in a new window" because I can view the extra information, close the tab and be back where I was without accidentally closing it before going back. I think that's a better default.

Additionally, we were talking about the "additional options" section being a good place for things we want on by default, but users might want ti disable. I think we should include "Open in new Window" in that as well.

[streamich]

#86902