Context

OpenAIGenerateImageFunctionalTest fails not always but regularly.
Locally triggered tests show that this is mainly - likely only - due to too short "waiting time".
Or in other words ... looks like it takes now longer until the image is generated and visible on the UI.

2 problems:

• generating the image may take a bit of time ... we have no control overthe response time of the 3rd-party-systems. => give a looot of wait time
• the instance also may suffer from lack of performance. E.g.
  • new asset (jcr-asset) not yet visible on asset-app grid
  • failure on login

Tasks

#generateAsset  ; #waitForImagesToBeGenerated

OpenAIGenerateImageFunctionalTest#generateAsset ... should wait longer until image is generated.

Improve OpenAiGenerateImageDialog#waitForImagesToBeGenerated add possibility to pass a parameter for the max. wait time
Also code a bit smelly, with a "nested Webdriver-wait". Simplify.

#deleteAsset

It apparently fails now and then by the login!
Which is quite bad.

Deleting the asset is not a great test.
We can keep the deletion for data-hygiene reasons ... but test should not fail if the deletion fails.

And deletion can be done in same method at the end, re-using same selenium-session without additional login.

Give asset a unique name

Otherwise, if deletion fails once, we get auto-generated asset-names.