Resolving an issue when DetailText receives undefined/null value

[codyrancher]

Summary

Fixes #13547

The repro steps outlined in the original issue are a little finicky. The secret gets immediately deleted from the backend so you only see on the same page load as doing the yaml import. If you refresh you'll need to import again.

Occurred changes and/or fixed issues

We now default to an empty string which allows the rest of the component to run as expected.

I also made the auth type components props optional since they can come back undefined. This resolves some console warnings.

While testing this it also became apparent we weren't properly redirecting to failwhale when a resource didn't exist. I added that functionality as well.

Areas or cases that should be tested

Anywhere that has <DetailText />. I think verifying in the secret detail page is sufficient.

Areas which could experience regressions

Same as above

Screenshot/Video

detail-text-null.mp4

Checklist

• The PR is linked to an issue and the linked issue has a Milestone, or no issue is needed
• The PR has a Milestone
• The PR template has been filled out
• The PR has been self reviewed
• The PR has a reviewer assigned
• The PR has automated tests or clear instructions for manual tests and the linked issue has appropriate QA labels, or tests are not needed
• The PR has reviewed with UX and tested in light and dark mode, or there are no UX changes
• The PR has been reviewed in terms of Accessibility