Not Automatically picking java kernel when opening a Java Notebook
Seems like it's failing pretty often (if not always) in raw, conda, 3.9, ubuntu-latest setup
screenshot confirms wrong kernel was selected

Still failing after the regression fix, I'm pretty sure CI machines do not have the kernel installed required for this test
This isn't a flaky tet issue, the code is broken, we're not listing all of the kernels correctly.
@IanMatthewHuff I tried to enable this test and found that the code was actually buggy, attempted fix is here https://github.com/microsoft/vscode-jupyter/pull/11053
Basically today we can run into situations where the kernels on disc are not shown. The problem is with the new code (changes as a result of) written to display the new kernel picker ux. Basically we have code that will fetch the controllers, and then subsequently we attempt to run the same method again and this sime the previous request is cancelled and that causes issues.
On a side note, the PR ensures that none of the cancellation tokens are nullable, if you follow the code path its impossible for them to be null, i.e. they are always valid.
Probably blocked on https://github.com/microsoft/vscode-jupyter/issues/11153 I say that because its possible that changes in #11153 would end up fixing this issue.
Adding my self, as I believe the problem is in the kernel finder (my area) and not necessarily in the code that matches kernels.
Should now be fixed