Add profiling support for DoubleValuesSource

### Description

Lucene now has great [profiling support](https://github.com/apache/lucene/blob/main/lucene/sandbox/src/java/org/apache/lucene/sandbox/search/QueryProfilerIndexSearcher.java) for understanding search-time costs. It provides detailed breakdowns of time spent across sub-queries and scorers.

I'm wondering if it makes sense to expand profiling support to other value-producing components, such as Lucene `DoubleValuesSource`. In Amazon Product Search, we make heavy use of this powerful dynamic expression features for search (such as filtering or scoring based on a runtime computed expression). So having a profiling for `DoubleValuesSource` could be really useful since we can track down slow ones and optimize. This could also benefit other users who rely on this feature as well.

I'm happy to draft a PR and iterate. Opening this issue to gather community feedback first.

Start by reading lucene/sandbox/src/java/org/apache/lucene/sandbox/search/QueryProfilerIndexSearcher.java, then investigate how profiling could extend to DoubleValuesSource in runtime filtering or scoring. Done means a concrete profiling design and implementation scope, with the community feedback requested by the issue resolved.

Written by the indexing model from the issue text.