* origin/topic/vern/script-opt-maint.Jun24:
script optimization baseline tweaks due to recent minor changes
updated list of BiFs for script optimization
addressed some Coverity nits
improved error cascade for invalid attributes
* topic/timw/prometheus-cpp-3: (35 commits)
Update docs submodule [nomail] [skip ci]
Add type aliases for instrument and family shared_ptrs
Update NEWS for double and is_sum changes
Remove is_sum arguments from counters and gauges
Change all instruments to only handle doubles
Add comment to telemetry::Manager::InitPostScript
Remove all of the ZEEK_METRICS_ environment variables
Fix header comments in scripts/policy/frameworks/telemetry/prometheus.zeek
Change all prometheus #includes to use angle brackets
Update zeekctl submodule for metrics_port node.cfg option
Regenerate docs [nomail]
Remove the is_sum argument from BIF histogram creation methods
Update NEWS for Telemetry rework
Remove Telemetry::metrics_export_prefixes option
Validate that label names are constant in non-zeek metrics
Avoid calling Collect() in counter/gauge Value() methods if not needed
Fix some determinism issues with btests
Temporarily disable the scripts/base/frameworks/telemetry/internal-metrics btest
Fix the scripts.policy.frameworks.telemetry.prometheus btest to use the service discovery endpoint
Btest updates due to recent changes
...
* topic/christian/analyzer-lookup-bifs:
More precise error reporting for the disable_analyzer() BiF
Add btests for the lookup_connection_analyzer_id() BiF.
Add BiF for looking up a connection's numeric protocol analyzer IDs
This replaces generic reporter->Error() calls with the builtin-specific variety,
which gives better context in the resulting error messages (such as the script
and line causing it).
Includes corresponding baseline update in one affected btest.
This adds a new lookup_connection_analyzer_id() BiF to find a given connection's
numeric identifier for a given protocol analyzer (as defined by the underlying
Analyzer::id_counter).
This enables users to call disable_analyzer(), which requires a numeric analyzer
ID, outside of analyzer_confirmation_info and analyzer_violation_info events
handlers.
