Add native released run to PR workflow

[michalvavrik]

Summary

closes #886

• Quarkus version is the released one as we already run daily's with 999-SNAPSHOT but don't check released one. Running both seems expensive (waiting time).
• No sense to check for Quarkus 1.x version as thanks to Jakarta migration there is no chance it would work anyway
• Don't validate framework twice, instead store result as maven repo, which allows me in next run not to re-run "framework" profile anyway (yes, it's very fast, but when I specify -pl examples/xyz it wouldn't run)

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

[michalvavrik]

Seems like a network blips, will rerun.

[mjurc]

Thanks a lot for making this workflow better.