Chore: Fix order of Kubernetes versions in Compatibility matrix

[rohanKanojia]

• latest Kubernetes Versions should be shown first followed by older versions
• Added column for 1.16.0 as discussed in Support for kubernetes 1.16 #2509
• Added column for OpenShift 4.5.14(after running integration tests on crc)

Description

Type of change

• Bug fix (non-breaking change which fixes an issue)
• Feature (non-breaking change which adds functionality)
• Breaking change (fix or feature that would cause existing functionality to change
• Chore (non-breaking change which doesn't affect codebase;
  test, version modification, documentation, etc.)

Checklist

• Code contributed by me aligns with current project license: Apache 2.0
• I Added CHANGELOG entry regarding this change
• I have implemented unit tests to cover my changes
• I have added/updated the javadocs and other documentation accordingly
• No new bugs, code smells, etc. in SonarCloud report
• I tested my code in Kubernetes
• I tested my code in OpenShift

[manusa]

This looks awkard. I think it will raise more questions rather than helping.

[rohanKanojia]

Thanks for noticing, looks like I missed it 👀

[sonarqubecloud]

Kudos, SonarCloud Quality Gate passed!

0 Bugs
0 Vulnerabilities (and 0 Security Hotspots to review)
0 Code Smells

No Coverage information
No Duplication information

The version of Java (1.8.0_265) you have used to run this analysis is deprecated and we will stop accepting it from October 2020. Please update to at least Java 11.
Read more here

[manusa]

[merge]