[Reporting] adjust esquery refreshes settings

[tsullivan]

Summary

https://www.elastic.co/guide/en/elasticsearch/reference/current/docs-refresh.html

The goal is to use a refresh value of "wait_for" or false for Reporting's Index, Update, Delete, and Bulk operations, to limit negative impacts to search and indexing performance.

Checklist

Delete any items that are not applicable to this PR.

• Unit or functional tests were updated or added to match the most common scenarios

Risk Matrix

Before closing this PR, invite QA, stakeholders, and other developers to identify risks that should be tested prior to the change/feature release.

When forming the risk matrix, consider some of the following examples and how they may potentially impact the change:

Risk	Probability	Severity	Mitigation/Notes
Unexpected behavior in report job listing	Low	Medium	Users possibly may see report jobs out-of-sync with their state in the backend. This possibly will not be noticeable unless the user is watching the server logs in real-time while waiting for the report download to be available.

[tsullivan]

Without refresh after delete, this fetchJobs tends to predicable stale report artifacts for recently deleted reoprts in the list.

[elasticmachine]

Pinging @elastic/appex-sharedux (Team:SharedUX)

[kibana-ci]

💛 Build succeeded, but was flaky

• Buildkite Build
• Commit: 75b4590
• Cloud Deployment

Failed CI Steps

• FTR Configs #1

Metrics [docs]

Async chunks

Total size of all lazy-loaded chunks that will be downloaded as the user navigates the app

id	before	after	diff
reporting	59.2KB	59.1KB	-46.0B

Unknown metric groups

ESLint disabled line counts

id	before	after	diff
enterpriseSearch	19	21	+2
securitySolution	400	404	+4
total			+6

Total ESLint disabled count

id	before	after	diff
enterpriseSearch	20	22	+2
securitySolution	480	484	+4
total			+6

History

• 💚 Build #127588 succeeded cb41969
• 💚 Build #127012 succeeded 45590653dd4d03f615dafae4eaa3779094df1948
• 💚 Build #126967 succeeded 9e8858592e49eb84d0f2bcebc9e33abd422ed0f0

To update your PR or re-run it, just comment with:
@elasticmachine merge upstream

cc @tsullivan

[rshen91]

tested locally with sample data - reporting LGTM!