Explain why users will see an `extensions.csproj` in their project in "Setting up durable-py debugging"

[davidmrdavid]

Contributors may not understand why they need to carry and potentially edit a .NET configuration file in their Python project. It would be good to shine some light onto that and explain that, at most, they will only be expected to change the version numbers of their dependencies

[anthonychu]

I think in a couple of weeks we can assume people will use bundles and remove all references to .NET and .NET artifacts. If they need to test with custom version of the extension in the future, it’s a pretty advanced scenario that they should know how to deal with because they are probably already familiar with Functions.

[priyaananthasankar]

@anthonychu / @davidmrdavid : I will then mention a sample host.json file and remove specifics related to not using bundles - mainly these steps, shall be removed and one host.json file example will be provided that has extension bundles configured. Does that sound good?

"""
Setting up durable-py debugging
Use starter sample from this folder (TBD: add folder name).

If you want to debug a specific version of the Durable Extension, make the following changes: In host.json, remove the extensionsBundle portion to enable specific version debugging.

Provide a hub name (else remove the entire extensions portion to default to DurableFunctionsHub) Here's how the host.json should look like:

"""

{
  "version": "2.0",
  "extensions": {
    "durableTask": {
      "hubName": "{hubName}"
    }
  }
}

[priyaananthasankar]

As discussed with David, that section with extensions.csproj can be removed as the goal here is to hide the .NET details from the end user and focus on Python