Update proto for marshal issue

[rim99]

Which problem is this PR solving?

Resolves #4150

Description of the changes

• Make sure time fields works normally in generated go file

How was this change tested?

• Tested with PR Add optional time window in TraceGetParameters jaeger#6159

Checklist

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

[yurishkuro]

What does "works normally" mean? What wasn't working?

[rim99]

@yurishkuro Before this change, this test would fail
https://github.com/rim99/jaeger/blob/d00b4d3888475cb86668849b75246616fe3cb389/cmd/query/app/apiv3/grpc_handler_test.go#L81

It seems, server side cannot receive time values in request, and initialized these as 0001-01-01T00:00:00Z

[yurishkuro]

Before this change, this test would fail

I don't follow. The test is passing in the main repo, against the official proto. What specifically makes it fail?

[rim99]

The test in main repo doesn't test these 2 time fields. https://github.com/jaegertracing/jaeger/blob/main/cmd/query/app/apiv3/grpc_handler_test.go#L92-L94

In this proto file, tested time fields are here: https://github.com/jaegertracing/jaeger-idl/blob/main/proto/api_v3/query_service.proto#L60

I think we can either add more gogoproto extensions like current way, or remove these 2 existing gogoproto extension lines

(gogoproto.stdtime) = true

https://github.com/jaegertracing/jaeger-idl/blob/main/proto/api_v3/query_service.proto#L33-L37