Remove X preceding unmapped TypeURIs

[notque]

This change removes the practice of prepending an 'X' character to the typeURI field in CADF events when the resource type is not explicitly defined in the audit mapping configuration.

Problem:

Currently, when the audit middleware encounters an API path segment for which no resource mapping exists, it dynamically creates a specification. As part of this process, it prepends an 'X' to the derived resource name, which results in typeURIs like service/Xresource-name.

While this 'X' was intended as an internal indicator for developers to identify endpoints needing proper mapping, it appears in the final, customer-facing audit events. This causes confusion for users as the 'X' is undocumented and has no defined meaning from their perspective.

Solution:

The middleware already logs a clear warning message (e.g., unknown resource: (created on demand)) when it encounters an undefined resource type. This logging is sufficient for internal purposes (identifying missing mappings).

#112

[notque]

I'll fix tests later, I've been thinking about the broader issue about this all day, and wanted to get my thoughts down before the weekend.