chore(deps): Bump indexmap from 1.9.3 to 2.0.0

[dependabot]

Bumps indexmap from 1.9.3 to 2.0.0.

Changelog

Sourced from indexmap's changelog.

• 2.0.0

  • MSRV: Rust 1.64.0 or later is now required.

  • The "std" feature is no longer auto-detected. It is included in the default feature set, or else can be enabled like any other Cargo feature.

  • The "serde-1" feature has been removed, leaving just the optional "serde" dependency to be enabled like a feature itself.

  • IndexMap::get_index_mut now returns Option<(&K, &mut V)>, changing the key part from &mut K to &K. There is also a new alternative MutableKeys::get_index_mut2 to access the former behavior.

  • The new map::Slice<K, V> and set::Slice<T> offer a linear view of maps and sets, behaving a lot like normal [(K, V)] and [T] slices. Notably, comparison traits like Eq only consider items in order, rather than hash lookups, and slices even implement Hash.

  • IndexMap and IndexSet now have sort_by_cached_key and par_sort_by_cached_key methods which perform stable sorts in place using a key extraction function.

  • IndexMap and IndexSet now have reserve_exact, try_reserve, and try_reserve_exact methods that correspond to the same methods on Vec. However, exactness only applies to the direct capacity for items, while the raw hash table still follows its own rules for capacity and load factor.

  • The Equivalent trait is now re-exported from the equivalent crate, intended as a common base to allow types to work with multiple map types.

  • The hashbrown dependency has been updated to version 0.14.

  • The serde_seq module has been moved from the crate root to below the map module.

Commits

• 8e47be8 Merge pull request #267 from cuviper/release-2.0.0
• ad694fb Release 2.0.0
• b5b2814 Merge pull request #266 from cuviper/doc-capacity
• d3ea289 Document the lower-bound semantics of capacity
• 74e14da Merge pull request #264 from cuviper/equivalent
• 677c605 Add a relnote for Equivalent
• 6d83bc1 pub use equivalent::Equivalent;
• bb48357 Merge pull request #263 from cuviper/insert_in_slot
• c37dae6 Use hashbrown's new single-lookup insertion
• ee71507 Merge pull request #262 from daxpedda/hashbrown-v0.14
• Additional commits viewable in compare view

Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting @dependabot rebase.

---

Dependabot commands and options

You can trigger Dependabot actions by commenting on this PR:

• @dependabot rebase will rebase this PR
• @dependabot recreate will recreate this PR, overwriting any edits that have been made to it
• @dependabot merge will merge this PR after your CI passes on it
• @dependabot squash and merge will squash and merge this PR after your CI passes on it
• @dependabot cancel merge will cancel a previously requested merge and block automerging
• @dependabot reopen will reopen this PR if it is closed
• @dependabot close will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually
• @dependabot ignore this major version will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself)
• @dependabot ignore this minor version will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself)
• @dependabot ignore this dependency will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)

[bits-bot]

Thank you for your submission! We really appreciate it. Like many open source projects, we ask that you all sign our Contributor License Agreement before we can accept your contribution.
1 out of 2 committers have signed the CLA.

✅ dsmith3197
❌ dependabot[bot]
_{You have signed the CLA already but the status is still pending? Let us recheck it.}

[netlify]

✅ Deploy Preview for vector-project canceled.

Name	Link
🔨 Latest commit	442adb3
🔍 Latest deploy log	https://app.netlify.com/sites/vector-project/deploys/649c575e0c504100081a60c1

[netlify]

✅ Deploy Preview for vrl-playground ready!

Name	Link
🔨 Latest commit	442adb3
🔍 Latest deploy log	https://app.netlify.com/sites/vrl-playground/deploys/649c575ec447270008804945
😎 Deploy Preview	https://deploy-preview-17755--vrl-playground.netlify.app
📱 Preview on mobile	Toggle QR Code... Use your smartphone camera to open QR code link.

---

To edit notification comments on pull requests, go to your Netlify site configuration.

[datadog-vectordotdev]

Datadog Report

Branch report: dependabot/cargo/indexmap-2.0.0
Commit report: de1f095

✅ vector: 0 Failed, 0 New Flaky, 1902 Passed, 0 Skipped, 1m 31.46s Wall Time

[github-actions]

Regression Detector Results

Run ID: 38f8c404-822d-4c48-9630-e3562e0e8523
Baseline: e26e8b8
Comparison: 248ccb8
Total vector CPUs: 7

Explanation

A regression test is an integrated performance test for vector in a repeatable rig, with varying configuration for vector. What follows is a statistical summary of a brief vector run for each configuration across SHAs given above. The goal of these tests are to determine quickly if vector performance is changed and to what degree by a pull request.

Because a target's optimization goal performance in each experiment will vary somewhat each time it is run, we can only estimate mean differences in optimization goal relative to the baseline target. We express these differences as a percentage change relative to the baseline target, denoted "Δ mean %". These estimates are made to a precision that balances accuracy and cost control. We represent this precision as a 90.00% confidence interval denoted "Δ mean % CI": there is a 90.00% chance that the true value of "Δ mean %" is in that interval.

We decide whether a change in performance is a "regression" -- a change worth investigating further -- if both of the following two criteria are true:

1. The estimated |Δ mean %| ≥ 5.00%. This criterion intends to answer the question "Does the estimated change in mean optimization goal performance have a meaningful impact on your customers?". We assume that when |Δ mean %| < 5.00%, the impact on your customers is not meaningful. We also assume that a performance change in optimization goal is worth investigating whether it is an increase or decrease, so long as the magnitude of the change is sufficiently large.

2. Zero is not in the 90.00% confidence interval "Δ mean % CI" about "Δ mean %". This statement is equivalent to saying that there is at least a 90.00% chance that the mean difference in optimization goal is not zero. This criterion intends to answer the question, "Is there a statistically significant difference in mean optimization goal performance?". It also means there is no more than a 10.00% chance this criterion reports a statistically significant difference when the true difference in mean optimization goal is zero -- a "false positive". We assume you are willing to accept a 10.00% chance of inaccurately detecting a change in performance when no true difference exists.

The table below, if present, lists those experiments that have experienced a statistically significant change in mean optimization goal performance between baseline and comparison SHAs with 90.00% confidence OR have been detected as newly erratic. Negative values of "Δ mean %" mean that baseline is faster, whereas positive values of "Δ mean %" mean that comparison is faster. Results that do not exhibit more than a ±5.00% change in their mean optimization goal are discarded. An experiment is erratic if its coefficient of variation is greater than 0.1. The abbreviated table will be omitted if no interesting change is observed.

No interesting changes in experiment optimization goals with confidence ≥ 90.00% and |Δ mean %| ≥ 5.00%.

Fine details of change detection per experiment.

experiment	goal	Δ mean %	Δ mean % CI	confidence
syslog_log2metric_splunk_hec_metrics	ingress throughput	+4.25	[+4.15, +4.36]	100.00%
syslog_log2metric_humio_metrics	ingress throughput	+3.49	[+3.41, +3.57]	100.00%
syslog_regex_logs2metric_ddmetrics	ingress throughput	+2.87	[+2.59, +3.15]	100.00%
http_text_to_http_json	ingress throughput	+2.37	[+2.31, +2.43]	100.00%
syslog_loki	ingress throughput	+2.22	[+2.16, +2.29]	100.00%
socket_to_socket_blackhole	ingress throughput	+1.94	[+1.88, +2.00]	100.00%
syslog_humio_logs	ingress throughput	+1.44	[+1.37, +1.51]	100.00%
splunk_hec_route_s3	ingress throughput	+1.43	[+1.28, +1.58]	100.00%
otlp_grpc_to_blackhole	ingress throughput	+1.07	[+0.96, +1.18]	100.00%
syslog_splunk_hec_logs	ingress throughput	+0.62	[+0.55, +0.70]	100.00%
http_to_http_noack	ingress throughput	+0.04	[-0.01, +0.10]	68.63%
enterprise_http_to_http	ingress throughput	+0.03	[-0.01, +0.06]	70.44%
splunk_hec_indexer_ack_blackhole	ingress throughput	+0.01	[-0.03, +0.05]	17.15%
fluent_elasticsearch	ingress throughput	+0.00	[+0.00, +0.00]	84.59%
http_to_http_json	ingress throughput	-0.01	[-0.05, +0.03]	19.09%
splunk_hec_to_splunk_hec_logs_acks	ingress throughput	-0.01	[-0.07, +0.05]	15.58%
splunk_hec_to_splunk_hec_logs_noack	ingress throughput	-0.03	[-0.07, +0.02]	54.15%
http_to_http_acks	ingress throughput	-0.33	[-1.55, +0.89]	26.91%
datadog_agent_remap_datadog_logs_acks	ingress throughput	-0.53	[-0.64, -0.41]	100.00%
file_to_blackhole	egress throughput	-0.72	[-4.47, +3.02]	19.62%
datadog_agent_remap_blackhole_acks	ingress throughput	-1.49	[-1.55, -1.44]	100.00%
datadog_agent_remap_datadog_logs	ingress throughput	-1.63	[-1.73, -1.53]	100.00%
otlp_http_to_blackhole	ingress throughput	-1.93	[-2.11, -1.75]	100.00%
datadog_agent_remap_blackhole	ingress throughput	-1.95	[-2.04, -1.86]	100.00%