settings: Remove settings related to upstream python REPL

[austin3dickey]

This PR removes the python.REPL.* settings that come from the upstream, which aren't useful in Positron since we don't use the python REPL.

Release Notes

New Features

• N/A

Bug Fixes

• Removed some redundant settings related to the upstream python REPL (Hide Python settings related to upstream REPL features #5602)

QA Notes

I validated that these settings don't appear in the settings menu anymore.

[github-actions]

All contributors have signed the CLA ✍️ ✅
_{Posted by the CLA Assistant Lite bot.}

[github-actions]

E2E Tests 🚀
This PR will run tests tagged with: @critical

^{readme  valid tags}

[austin3dickey]

I have read the CLA Document and I hereby sign the CLA

[austin3dickey]

lint failure is due to #5930

[juliasilge]

There is nothing for us to do to help manage the upstream merges for JSON files, is there? Should we add a note about this to https://connect.posit.it/positron-wiki/overlay-strategy.html?

[petetronic]

There is nothing for us to do to help manage the upstream merges for JSON files, is there? Should we add a note about this to https://connect.posit.it/positron-wiki/overlay-strategy.html?

In many other JSON files we've added // --- style comments, even if it is not official JSON syntax, the benefit has outweighed the strictness of syntax and those have been tolerated by scripts and applications. We could test it would be tolerated in these particular files to help future merging / code documentation first? If we run into issues, agree we could document it externally as a back up.

[austin3dickey]

We could test it would be tolerated in these particular files to help future merging / code documentation first

Yeah, it turns out that they really don't like comments in package.json files.

npm ERR! code EJSONPARSE
npm ERR! path /home/runner/work/positron/positron/extensions/positron-python/package.json
npm ERR! JSON.parse Expected double-quoted property name in JSON at position 33261 while parsing near "... },\n                // --- Start Positro..."
npm ERR! JSON.parse Failed to parse JSON data.
npm ERR! JSON.parse Note: package.json must be actual JSON, not just JavaScript.

So I won't include the comments in the JSON files, and I'll add a little note in the wiki.

[austin3dickey]

ah yeah, looks like some tests that change the settings to the non-default value are failing. I suppose I'll remove those tests.

[austin3dickey]

Okay this should be ready for review!

[isabelizimm]

There are some funky formatting inconsistencies between positron and the positron-python (that hopefully should be resolved soon with #5838) that can result in this weirdness via format-on-save 😩

Are you able to remove these unrelated whitespace changes? I believe the easiest way is to command palette Format Document from inside the extensions/positron-python workspace.

[austin3dickey]

Sure! I originally kept them because they seemed like improvements, but I can remove them from this PR since they're unrelated.

[austin3dickey]

Oh I see, we inherited the weirdness from the upstream. :)

[isabelizimm]

Looks good to me! I also tried it out locally and could not sniff out any non-Positron REPL settings 🎉

[juliasilge]

Thank you so much!