Remove idempotency token for Athena queries

[fiskus]

Description

TODO

• Unit tests
• Automated tests (e.g. Preflight)
• Documentation
  • Python: Run build.py for new docstrings
  • JavaScript: basic explanation and screenshot of new features
• Changelog entry

[codecov]

Codecov Report

Merging #2992 (066affb) into master (4f84147) will increase coverage by 0.01%.
The diff coverage is n/a.

@@            Coverage Diff             @@
##           master    #2992      +/-   ##
==========================================
+ Coverage   38.79%   38.81%   +0.01%     
==========================================
  Files         623      623              
  Lines       27635    27621      -14     
  Branches     4013     4008       -5     
==========================================
  Hits        10720    10720              
+ Misses      15770    15757      -13     
+ Partials     1145     1144       -1     

Flag	Coverage Δ
api-python	90.71% <ø> (ø)
catalog	12.26% <ø> (+<0.01%)	⬆️
lambda	87.29% <ø> (ø)

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

Impacted Files	Coverage Δ
...g/app/containers/Bucket/Queries/requests/athena.ts	0.00% <ø> (ø)

📣 We’re building smart automated test selection to slash your CI/CD build times. Learn more

[nl0]

why do we need this change? is idempotency useless in this case?

[fiskus]

Documentation is a little confusing: it says that two requests with the same token will return the same query. It doesn't say about results. So, probably it means two simultaneously executed queries will execute only one query if they share the same token. But it seems it's already done internally by SDK, and this token is not required (they articulate it in docs, that it's not required)
And preserving this token in code can lead to bugs, and it's just unnecessary to maintain something we don't need.

---

TLDR:

1. It's not required
2. It can produce errors and additional work to maintain