Description of problem:
As a user, I want to use the topology export feature again and again without seeing any errors. The export restart (when export is already running) or starting a new export removes the Export resource and recreates it. This results sometimes in an error which is shown as a toast notification to the user.

Version-Release number of selected component (if applicable):
4.9 and 4.10

How reproducible:
Sometimes. It looks like this is depending on your network speed.

Steps to Reproduce:
1. Install primer operator (tested with version 0.0.5)
2. Create a new namespace and import an application
3. Open topology and click on Export Application

Repeat until you can see an error:

4a) While the export is running click on Export Application again. In your browser network inspector, you can see that this triggers a DELETE and POST directly after another. This POST sometimes fails because the resource is not '100% deleted' yet.

4b) After the export is finished the Export Application button can be clicked again to start a new export. If the old Export resource is still available you can see a GET, DELETE and POST call as well.

Actual results
Sometimes it fails to create the Export resource.

Expected results:
This should 'always' work. It looks like this is dependent on some race conditions. Instead of doing both calls directly after another, we should wait (watcher?) until the Export resource is deleted before we create a new one.

Additional info:
See attached videos. Both videos are recorded at the same time against the same cluster.