Switch to ansi_up for ansi rendering in actions

[silverwind]

Fixes: #24777

[delvh]

But apart from that LGTM

[silverwind]

@wxiaoguang can you help me update these tests? They talk about some bugs in AnsiToHTML but those seem not present in ansi_up from cursory testing.

[silverwind]

Tests are now passing, but I'm not 100% certain the results are as expected. There are a number of style="color:rgb(255,255,255)" outputs, but actions log itself does not have this white color for uncolored text which seems odd.

[silverwind]

Ready again. I've moved the function and tests to separate files and restored all previous tests. The only test modification I did was to replace the previous ansi_to_html tests with test cases that call the function.

The problem with the style="color:rgb(255,255,255)" was that a ansi_up instance is stateful so when one test opened and not closed the color tag, it remembered that for future invocations. I removed this issue now by creating a fresh instance on every function call.

The seemingly odd AnsiUp.default || AnsiUp seems necessary so that the module correctly imports in both vitest and the browser, which I think is an issue related to their legacy AMD wrapper that the module features.