Change the example file name. Because managed identity is generally better than connection strings, don't imply that we're using connection strings.

Bumps the dotnet group in /docs/ai/tutorials/snippets/llm-eval with 1 update: [Microsoft.SemanticKernel](https://github.com/microsoft/semantic-kernel).


Updates `Microsoft.SemanticKernel` from 1.17.2 to 1.18.2
- [Release notes](https://github.com/microsoft/semantic-kernel/releases)
- [Commits](microsoft/semantic-kernel@dotnet-1.17.2...dotnet-1.18.2)

---
updated-dependencies:
- dependency-name: Microsoft.SemanticKernel
  dependency-type: direct:production
  update-type: version-update:semver-minor
  dependency-group: dotnet
...

Signed-off-by: dependabot[bot] <[email protected]>
Co-authored-by: dependabot[bot] <49699333+dependabot[bot]@users.noreply.github.com>

The EventPipe docs were saying things about LTTng that were either incorrect or misleading. I think changing the comparison to use perf_events makes it more effective.

- LTTng does support tracing kernel events, but as written users are likely to get the wrong idea. Perfcollect, the tool we recommend to when using LTTng with .NET, uses perf_events rather than LTTng to perform the kernel tracing. Perfcollect only uses lttng for its user-mode tracing capability.
- LTTng doesn't support native callstacks as far as I am aware.

Sets the output sample's code type to `text` to avoid CLI type highlighting.

Markdown lint fix

…n published apphost (#42397)