Add a retry to the secure_report QA page component

What does this MR do?

Adds a retry when checking for vulnerabilities on the Security Dashboard. This should mitigate the issue seen on Staging - #235109 (closed) While that issue was never replicated locally (even pointing to staging), it is hoped that this retry will allow the test to retry if the page is parsed when no results are loaded.

Screenshots

https://gitlab.com/gitlab-org/gitlab/uploads/7716f197aedeb9b29d92fafcaa784f2e/secure_security_dashboard_in_a_project_shows_vulnerability_details.png

Does this MR meet the acceptance criteria?

Conformity

• Changelog entry
• Documentation (if required)
• Code review guidelines
• Merge request performance guidelines
• Style guides
• Database guides
• Separation of EE specific content

Availability and Testing

• Review and add/update tests for this feature/bug. Consider all test levels. See the Test Planning Process.
• Tested in all supported browsers
• Informed Infrastructure department of a default or new setting change, if applicable per definition of done

Security

If this MR contains changes to processing or storing of credentials or tokens, authorization and authentication methods and other items described in the security review guidelines:

• Label as security and @ mention @gitlab-com/gl-security/appsec
• The MR includes necessary changes to maintain consistency between UI, API, email, or other methods
• Security reports checked/validated by a reviewer from the AppSec team