Detect unexecuted code in tests

Unreachable, or "dead", code is often a symptom that something has been missed unintentionally in the codebase. Dead code in your test suite is even more problematic because it means some part of your code that you thought will test something is, well, not serving its purpose. We've just added a new issue, TCV-002, in the Test Coverage Analyzer that'll alert you whenever it finds unexecuted code in any test files.

New in Analyzers

• Java: 5 new issues (JAVA-A1027, JAVA-A1028, JAVA-A1029, JAVA-A1030, JAVA-S1031)
• PHP: 3 new issues (PHP-W1083, PHP-W1087, PHP-W1088)
• Go: 12 new issues for go.etcd.io/etcd/client/v3 (GO-E1003, GO-R1001, GO-R1002, GO-W1003); 4 new issues for gorm.io/gorm (GO-E1004, GO-E1005, GO-W1004, GO-W1005); and 4 new general issues (GO-E1006, GO-E1007, GO-S1029, GO-W1006)
• C#: 14 new issues (CS-W1016, CS-W1017, CS-W1018, CS-W1019, CS-W1020, CS-W1021, CS-R1039, CS-R1040, CS-P1005, CS-P1006, CS-A1008, CS-A1009, CS-A1010, CS-S1000)

Fixes and improvements

• Users will now get directly directed to the organization they accepted an invite for.
• Issues under a run are now paginated, allowing users to see all of them directly without explicitly searching for them.
• Billing checkout page didn't show the applied credits. This has been fixed.