make bigsampler bq output partition configurable

[benkonz]

adds a new arg to BigSampler called bigqueryPartitioning, defaults to "DAY", which should maintain the same behavior as before. Users can pass in "DAY|HOUR|MONTH|YEAR", as well as NULL if no table partitioning is desired.

Making this change so that Ratatool works better with Spotify's internal Luigi BigQuery tasks, which use table sharding as partitioning, and when ratatool sets the partitioning to ingestion day, it causes problems with retention.

Tested by outputting this table via this workflow:

apiVersion: workflow.data.spotify.com/v1alpha1
kind: Workflow
metadata:
  name: ratatool-internal-examples-stream-days-bigsampler
  namespace: data-quality-spotify
spec:
  resourceID: ratatool-internal-examples.stream.days.BigSampler
  componentID: ratatool-internal
  scheduling:
    schedule: daily
  serviceAccountRef:
    external: contours-test-pipeline@data-quality-spotify.iam.gserviceaccount.com
  docker:
    args:
      - 'wrap-luigi'
      - '--module'
      - 'luigi_tasks'
      - 'BigSampler'
      - '--uri-prefix'
      - 'gs://benk-playground'
      - '--project'
      - 'data-quality-spotify'
      - '--service-account'
      - 'contours-test-pipeline@data-quality-spotify.iam.gserviceaccount.com'
      - '--input-endpoint'
      - 'spotify-people:groups.groups_%Y%m%d'
      - '--output-endpoint'
      - 'data-quality-spotify:benk_test_eu.benk_test_eu_%Y%m%d'
      - '--sample'
      - '0.01'
      - '--partition'
      - '{}'
    terminationLogging: true
    image: 43ea5c916cd5a85623bf0de598da15982c29d8952dbf63a068d10e5b56466e61
  workflowAlertingDisabled: true

the 43ea5c916cd5a85623bf0de598da15982c29d8952dbf63a068d10e5b56466e61 docker image is using my local ratatool PR's code via sbt publishM2

the linked table has to partitioning and uses the sharding generated by the BigQueryTarget in Luigi

here is another table that is using the --bigquery-partitioning arg to set the partitioning to "MONTH".

[codecov]

Codecov Report

Attention: Patch coverage is 25.00000% with 6 lines in your changes are missing coverage. Please review.

Project coverage is 70.91%. Comparing base (f637e88) to head (6ed1bbf).
Report is 8 commits behind head on master.

Files	Patch %	Lines
...ala/com/spotify/ratatool/samplers/BigSampler.scala	33.33%	4 Missing ⚠️
...spotify/ratatool/samplers/BigSamplerBigQuery.scala	0.00%	2 Missing ⚠️

Additional details and impacted files

@@            Coverage Diff             @@
##           master     #705      +/-   ##
==========================================
- Coverage   71.09%   70.91%   -0.18%     
==========================================
  Files          44       44              
  Lines        1816     1822       +6     
  Branches      292      301       +9     
==========================================
+ Hits         1291     1292       +1     
- Misses        525      530       +5     

Flag	Coverage Δ
ratatoolCli	2.90% <0.00%> (-0.02%)	⬇️
ratatoolCommon	0.00% <ø> (ø)
ratatoolDiffy	32.73% <0.00%> (-0.13%)	⬇️
ratatoolExamples	17.34% <0.00%> (-0.07%)	⬇️
ratatoolSampling	62.11% <25.00%> (-0.26%)	⬇️
ratatoolScalacheck	78.14% <ø> (ø)
ratatoolShapeless	4.18% <0.00%> (-0.02%)	⬇️

Flags with carried forward coverage won't be shown. Click here to find out more.

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

[monzalo14]

I'd love if you could separate formatting changes from actual changes, but LGTM!

[monzalo14]

Nit: Is it possible to separate formatting changes into a different PR?

[benkonz]

not really, since I'm aligning the new whitespace with the field being added in this PR