Adding suport for attributes in v3 traces querying

[pranjalg1331]

Which problem is this PR solving?

Resolves #7594

Description of the changes

I added support for filtering the traces based on attributes passed.

How was this change tested?

• I checked the response I got from the GET request and it showed the correct filtered data.
  http://localhost:16686/api/v3/traces?query.num_traces=1&query.service_name=frontend&query.start_time_max=2025-10-19T15%3A54%3A58.373570048Z&query.start_time_min=2025-10-16T14%3A54%3A59.373570048Z&query.attributes={%22driver%22%3A%22T704822C%22}

Checklist

• [ x] I have read https://github.com/jaegertracing/jaeger/blob/master/CONTRIBUTING_GUIDELINES.md
• [ x] I have signed all commits
• I have added unit tests for the new functionality
• [x ] I have run lint and test steps successfully
  • for jaeger: make lint test
  • for jaeger-ui: npm run lint and npm run test

[pranjalg1331]

I also noticed that attributes is not mentioned in Swagger docs.
Also, when querying the traces, the limit was passed as "num_traces" instead of search_depth
@yurishkuro Should I raise a pr adding these changes manually in jaeger-idl?

[yurishkuro]

Should I raise a pr adding these changes manually in jaeger-idl?

yes otherwise this change violates the schema

[pranjalg1331]

I have a created a pr for docs update.
@yurishkuro please review 😃