[actions] every action execution showing evidence of refresh: wait_for

[pmuellr]

During some analysis of alert and action duration timings, it appears actions are paying a cost of refresh:wait_for latency. We should investigate to see if we can change this.

For alerting, I noticed we turned it false, here:

kibana/x-pack/plugins/alerting/server/task_runner/task_runner.ts

Lines 522 to 532 in ad9f1c3

	try {
	await partiallyUpdateAlert(client, alertId, attributes, {
	ignore404: true,
	namespace,
	refresh: false,
	});
	} catch (err) {
	this.logger.error(
	`error updating alert execution status for ${this.alertType.id}:${alertId} ${err.message}`
	);
	}

And I'm thinking this is the primary way alerts are updated now (partially), when we re-org'd that.

So we can probably do the same for actions, but of course will need to review the interactions in the action SO's to make sure this is ok.

[elasticmachine]

Pinging @elastic/kibana-alerting-services (Team:Alerting Services)

[YulNaumenko]

Related PR #99919

[YulNaumenko]

Closing in favor of the existing issue, which has more context and currently is in the To-Do of Alerting project board