ANSI Control Sequence parsing and Project Log timestamps

[tlmii]

The primary purpose of this PR is enabling ANSI Control Sequence parsing to pass colors through from project logs to the log viewer. It does a few other things along the way, so here's the rundown:

1. Logs are HTML Encoded before being sent to the browser, other than the spans that are added as part of the ANSI parsing
2. The current "theme" of the log colors is based on the default Windows Terminal colors scheme. Fairly easy to change it if we want something else
3. Enabling the colors to be passed through during output redirection is enabled via an environment variable injected into each project when it is run
4. Since we're enabling colors, we also went ahead and enabled timestamps, and specified a format that (roughly) matches what the container logs output so that they're comparable
5. When parsing the ANSI Control Sequences we try to just drop any sequences we recognize don't handle. It's possible we will get some feedback that we missed a class of common sequences that we need to detect and drop.

The formatting of project logs with timestamps enabled looks off. It's clear that lines 2-n of each log entry were indented based on the info/warn/dbug/etc messages in line 1 but NOT anticipating the timestamps. We may want to consider adjusting the indentation ourselves in this case, but I'll save that for another PR after feedback (need to see what would happen with the docker logs in the same scenario as well).

Resolves https://github.com/dotnet/aspire-private-planning/issues/664 and resolves https://github.com/dotnet/aspire-private-planning/issues/610

[tlmii]

Screenshot:

[davidfowl]

LGTM

[eerhardt]

Can we make this configurable? I would rather see the time stamps in my own time zone when running locally.

[davidfowl]

I was thinking the same, it should be local

[tlmii]

Yeah, it was my intention that it'd be configurable eventually. I just started off for this PR with matching the docker logs (RFC3339 and UTC, which doesn't appear to be configurable) since it seemed being able to compare timestamps would be useful. I filed #115 to track making the project logs timestamp format/tz configurable.