Consider testing the debugger with ipykernel too

[jtpio]

The latest prereleases of ipykernel now include support for debugging: https://pypi.org/project/ipykernel/6.0.0rc0/

We should consider testing against it in the various tests in https://github.com/jupyterlab/jupyterlab/tree/master/packages/debugger/test.

For now it is assumed ipykernel does not support debugging here, but this is going to change soon:

jupyterlab/packages/debugger/test/service.spec.ts

Lines 89 to 100 in 3a3b401

	describe('#isAvailable', () => {
	it('should return true for kernels that have support for debugging', async () => {
	const enabled = await service.isAvailable(xpython);
	expect(enabled).toBe(true);
	});
	it('should return false for kernels that do not have support for debugging', async () => {
	const enabled = await service.isAvailable(ipykernel);
	expect(enabled).toBe(false);
	});
	});
	});

This will also help ensure new features are not developed for one kernel only. Or they should at least not drastically degrade the experience for those that don't implement them yet.

As some point, there will also be more end to end testing of the debugger using Galata (#10359).

[jtpio]

Closing as we now have mocks for the kernel specs in the debugger tests:

jupyterlab/packages/debugger/test/utils.ts

Lines 12 to 37 in e9a82c3

	export const KERNELSPECS: JSONObject = {
	default: 'xpython',
	kernelspecs: {
	python3: {
	name: 'Python',
	spec: {
	language: 'python',
	argv: [],
	display_name: 'Python 3',
	env: {}
	},
	resources: {}
	},
	xpython: {
	name: 'xpython',
	spec: {
	language: 'python',
	argv: [],
	display_name: 'xpython',
	env: {},
	metadata: { debugger: true }
	},
	resources: {}
	}
	}
	};

And UI Tests progressively covering more and more of the debugger features (which use ipykernel)