getKernelConnectionId doesn't always work

[DonJayamanne]

See comments here by @IanMatthewHuff #4192 (comment)

Ideally this function should always return the same thing regarless of the environment & interpreter selected.
One possible suggestion is to not include the property kernelConneciton.interpreter when computing the kernel Connection Id.

I think this needs to be addressed, else this function doesn't really return a unique id.
If resolved, then we can use this function in places like the function where we're checking if the kernel spec is the same or not (see this PR #4192 (comment)).

I.e. have a single way to compare kernel connection metadata

[DonJayamanne]

This issue was added as we could not use getKernelConnectionId to address the issue in #4192 & #4109
However that's caused by an upstream VS Code bug, hence there's no need to fix this bug #4332