Drop Elasticsearch throttling on Ingestion Server

[krysal]

Fixes

Fixes #3977 by @krysal

Description

We haven't need to throttle ES for a while. We could do a live test deploying this immediately and start a data refresh before the scheduled for next week.

Testing Instructions

Run a data refresh and confirms it continues to work properly.

Checklist

• My pull request has a descriptive title (not a vague title likeUpdate index.md).
• My pull request targets the default branch of the repository (main) or a parent feature branch.
• My commit messages follow best practices.
• My code follows the established code style of the repository.
• [n/a] I added or updated tests for the changes I made (if applicable).
• [n/a] I added or updated documentation (if applicable).
• I tried running the project locally and verified that there are no visible errors.
• [n/a] I ran the DAG documentation generator (ov just catalog/generate-docs for catalog PRs) or the media properties generator (ov just catalog/generate-docs media-props for the catalog or ov just api/generate-docs for the API) where applicable.

Developer Certificate of Origin

Developer Certificate of Origin

Developer Certificate of Origin
Version 1.1

Copyright (C) 2004, 2006 The Linux Foundation and its contributors.
1 Letterman Drive
Suite D4700
San Francisco, CA, 94129

Everyone is permitted to copy and distribute verbatim copies of this
license document, but changing it is not allowed.


Developer's Certificate of Origin 1.1

By making a contribution to this project, I certify that:

(a) The contribution was created in whole or in part by me and I
    have the right to submit it under the open source license
    indicated in the file; or

(b) The contribution is based upon previous work that, to the best
    of my knowledge, is covered under an appropriate open source
    license and I have the right under that license to submit that
    work with modifications, whether created in whole or in part
    by me, under the same open source license (unless I am
    permitted to submit under a different license), as indicated
    in the file; or

(c) The contribution was provided directly to me by some other
    person who certified (a), (b) or (c) and I have not modified
    it.

(d) I understand and agree that this project and the contribution
    are public and that a record of the contribution (including all
    personal information I submit with it, including my sign-off) is
    maintained indefinitely and may be redistributed consistent with
    this project or the open source license(s) involved.

[AetherUnbound]

No objections, but I do wonder if this is something we need to change right now. We'll be removing the ingestion server eventually, so I'm hesitant to make changes to it that could be deferred until after that time. Plus, it might be easier to test this once everything is on Airflow! Just a thought though, we'll have to do an ingestion server deployment this week anyway because of #4667 🙂

[krysal]

@AetherUnbound The data refresh operated without a limit before the issue introduced by the filtered index addition (which is already solved), so we won't make brand changes anyway, no much to test here I think. I wanted to make it since we'll deploy the ingestion server again (maybe the last one!).