Fix for dotnet-isolated function app debugging hang issue

[kshyju]

This is a follow up PR to fix the bug introduced in #8435

Context:
In #8435, I added code to log the tooling log messages using a new logger for which the log level is always set to Informational. My PR had a bug where I was stripping out the special prefix(azfuncjsonlog:)of the log messages before sending it to the logger. This caused core-tools to not handle this messages properly.

Impact of this bug:
Visual studio debugging for dotnet-isolated functions apps will hang.

Fix:
In this PR, I deleted the code which stripped the prefix so that the message is sent as it is to the logger. Now coretools will handle messages with this prefix as expected.

Pull request checklist

• My changes do not require documentation changes
  • Otherwise: Documentation issue linked to PR
• My changes should not be added to the release notes for the next release
  • Otherwise: I've added my notes to release_notes.md
• My changes do not need to be backported to a previous version
  • Otherwise: Backport tracked by issue/PR #issue_or_pr
• My changes do not require diagnostic events changes
  • Otherwise: I have added/updated all related diagnostic events and their documentation (Documentation issue linked to PR)
• I have added all required tests (Unit tests, E2E tests)

Validation

1. Created a new version of "Microsoft.Azure.WebJobs.Script.WebHost" nuget package with the host changes.
2. Consumed that nuget version in CoreTools (Azure.Functions.CLI)
3. Copied the build output of the Azure.Functions.CLI project and replaced it in the "cli_x64" of the release used by VS in local computer.
4. Verified debugging works.
5. Also verified the temporary file which VS uses (to which Coretools will write the message which include the process id).