Fix unexpected reader_type kwarg error

[yankevn]

Summary

This change always pops the reader_type keyword argument, regardless of whether the encoding is identity or not.

Rationale

We have had jobs fail due to using Parquet content type and Gzip file encoding. This change fixes that bug.

Changes

• Always pop the reader_type kwarg

Impact

All calls to s3_file_to_table will have the reader_type kwarg automatically popped, unless the reader type is daft or partial_file_download_params are defined.

Testing

• added a unit test
• Job run succeeded on beta stack
  • https://us-east-1.console.aws.amazon.com/states/home?region=us-east-1#/v2/executions/details/arn:aws:states:us-east-1:731308025943:execution:EC2WorkflowSfnCompactionEC2StateMachine03D9583F-sY9mlIoEkDAT:4d2cd46f-c15b-4a37-9f27-587f310742ae

Regression Risk

Low

Checklist

• Unit tests covering the changes have been added

  • If this is a bugfix, regression tests have been added

• E2E testing has been performed

Additional Notes

Any additional information or context relevant to this PR.

[raghumdani]

Looks good.