Allow to pass ES_TIME_RANGE var to Spark dependencies job

[Gr1N]

Which problem is this PR solving?

• https://github.com/jaegertracing/spark-dependencies allows using variable ES_TIME_RANGE to specify how far in the past the job should look to for spans. But that variable is missing in the operator. PR simply adds the possibility to pass the required variable.

Short description of the changes

• added elasticsearchTimeRange configuration option for Jaeger dependencies section

[Gr1N]

@jpkrohling @kevinearls review please

[jpkrohling]

LGTM

[Gr1N]

@jpkrohling please review again, I've fixed formatting

[Gr1N]

@jpkrohling I'm sorry but can you please check PR again? This time I walked through contributing guide and ran everything except e2e tests. Hope everything is ok now.

[codecov]

Codecov Report

Merging #1481 (6e71fb2) into master (b9d1e02) will increase coverage by 0.00%.
The diff coverage is 100.00%.

@@           Coverage Diff           @@
##           master    #1481   +/-   ##
=======================================
  Coverage   87.20%   87.21%           
=======================================
  Files          90       90           
  Lines        5003     5004    +1     
=======================================
+ Hits         4363     4364    +1     
  Misses        484      484           
  Partials      156      156           

Impacted Files	Coverage Δ
pkg/apis/jaegertracing/v1/jaeger_types.go	100.00% <ø> (ø)
pkg/cronjob/spark_dependencies.go	93.26% <100.00%> (+0.06%)	⬆️

---

Continue to review full report at Codecov.

Legend - Click here to learn more
Δ = absolute <relative> (impact), ø = not affected, ? = missing data
Powered by Codecov. Last update b9d1e02...6e71fb2. Read the comment docs.

[rubenvp8510]

I don't think the e2e failing is related to the changes made in this PR.

There is an issue with the ingress test, which should be fixed by this PR: #1491 As soon as that PR is merged could you rebase?

[Gr1N]

@rubenvp8510 yep, no problem

[jpkrohling]

PR rebased.

[Gr1N]

@jpkrohling thank you for the help and maybe you know when new version of the operator will be available to use?