Handle config secrets during build-time config detection

[michalvavrik]

Summary

addresses: quarkus-qe/quarkus-test-suite#1820 (comment)

All interceptors are registered by default and we don't create config ourselves, so cannot avoid registering secrets. It's irrelevant for build-time config detection.

Please check the relevant options

• Bug fix (non-breaking change which fixes an issue)
• New feature (non-breaking change which adds functionality)
• Dependency update
• Refactoring
• Breaking change (fix or feature that would cause existing functionality to change)
• This change requires a documentation update
• This change requires execution against OCP (use run tests phrase in comment)

Checklist:

• Example scenarios has been updated / added
• Methods and classes used in PR scenarios are meaningful
• Commits are well encapsulated and follow the best practices

[jedla97]

Thanks for quick fix! LGTM, CI is green and have quick run with affected testsuite test and it's works.