WaitFor for Elasticsearch

[Alirexaa]

Description

Adds WaitFor support for Elasticsearch

Related: #5645

Checklist

• Is this feature complete?
  • Yes. Ready to ship.
  • No. Follow-up changes expected.
• Are you including unit tests for the changes and scenario tests if relevant?
  • Yes
  • No
• Did you add public API?
  • Yes
    • If yes, did you have an API Review for it?
      • Yes
      • No
    • Did you add <remarks /> and <code /> elements on your triple slash comments?
      • Yes
      • No
  • No
• Does the change make any security assumptions or guarantees?
  • Yes
    • If yes, have you done a threat model and had a security review?
      • Yes
      • No
  • No
• Does the change require an update in our Aspire docs?
  • Yes
    • Link to aspire-docs issue:
  • No

Microsoft Reviewers: Open in CodeFlow

[mitchdenny]

/azp run

[azure-pipelines]

Azure Pipelines successfully started running 1 pipeline(s).

[mitchdenny]

Looks good to me (based on our current pattern).

[davidfowl]

The timeout in the test might be too low. I don't know how long elastic search takes to boot but its notoriously slow and unreliable from our other tests?

[davidfowl]

cc @radical note the changes

[eerhardt]

Is this really an hour? We are going to wait an hour for these tests? Isn't that just going to make us wait longer when the thing isn't responsive?

[radical]

This will become a problem whenever helix is backed up. The total timeout for the whole job is 90mins, so this will definitely timeout. Do we need to break this up?

aspire/eng/pipelines/azure-pipelines-public.yml

Lines 102 to 103 in 2344aaf

	# timeout accounts for wait times for helix agents up to 30mins
	timeoutInMinutes: 90

[radical]

The test run on this PR took ~8mins. If this is taking up to an hour sometimes then maybe we need to investigate why that is the case.