Add optional keepAssemblyContents to ParseAndCheckInteraction

[Jand42]

Adding a new optional parameter keepAssemblyContents to FsiEvaluationSession.ParseAndCheckInteraction.

This is a minor change that enables using an fsi session and also doing full content analysis on entered interactions. I have used a local build of my changes to make a WebSharper-enabled interactive session.

Question: would an overload be preferred instead of optional argument to keep binary compatibility? Or it's not a primary concern for FCS and code compatibility is enough?

[Jand42]

@dotnet-policy-service agree company="IntelliFactory"

[vzarytovskii]

This would be binary breaking. Which is not bad by default, just so it's a concious decision.

[Jand42]

@vzarytovskii I'm happy to make it non-breaking with an overload or differently named method (ParseAndCheckInteractionAndKeepAssemblyContents would be descriptive, but pretty long...). Please advise, thank you!

[vzarytovskii]

@vzarytovskii I'm happy to make it non-breaking with an overload or differently named method (ParseAndCheckInteractionAndKeepAssemblyContents would be descriptive, but pretty long...). Please advise, thank you!

Overload is usually good enough, but it's up to @T-Gro, if breaking change is fine or not.

[github-actions]

❗ Release notes required

---

✅ Found changes and release notes in following paths:

Change path	Release notes path	Description
src/Compiler	docs/release-notes/.FSharp.Compiler.Service/10.0.200.md

[T-Gro]

A sibling PR is removing switches for ML compat syntax anyway, so the upcoming FCS api will not be backwards compatible with the current one.

[T-Gro]

Thank you for the changes, this is good now @Jand42 .
Please add the release notes based on the instructions from the bot above 👍