Fix classic report ignoring category rules with messageRegex/traceRegex

[meganemura]

Context

categories.json rules with messageRegex or traceRegex never match any
test result in the classic report — only status-only rules (including the
built-in "Product defects" / "Test defects" fallbacks) do. For example:

{ "name": "Timeout", "matchedStatuses": ["failed"], "messageRegex": ".*timed out.*" }

A failing test whose message contains "timed out" still lands under
"Product defects" instead of "Timeout" — with no warning that the rule was
never even evaluated correctly.

Root cause: generators.ts builds the match input as {message, trace, status, flaky}, but categoryMatch in categories.ts destructures
statusMessage/statusTrace from it. The names never matched, so those
fields were always undefined, and match() treats undefined as a
non-match whenever a regex is set.

message/trace is the correct naming for this plugin: ClassicTestResult
is built on @allurereport/core-api's TestResult, whose error info is a
TestError ({message, trace, actual, expected}), and generators.ts
passes error?.message/error?.trace straight through under those same
keys.

statusMessage/statusTrace isn't a typo — it's the sibling plugin
plugin-allure2's field name. plugin-allure2/src/categories.ts has
identical matching logic, but that plugin's own data model
(Allure2TestResult) defines statusMessage/statusTrace directly, and
its caller passes those same keys — so that plugin isn't affected by this
bug. The two categories.ts files are close enough to be evidently related
implementations; this one ended up carrying the other model's field names.

Fix: destructure message/trace in categoryMatch, matching both
the caller and the underlying TestError type. Added a regression test
using the exact call shape generators.ts uses; also fixed 4 existing
tests that were unintentionally exercising a call shape the real caller
never uses.

Checklist

• Sign Allure CLA
• Provide unit tests

[CLAassistant]

All committers have signed the CLA.