Audit API routes don't correctly match resource IDs with a period

[micahlee]

Problem Description

When the resource ID used for retrieving audit events includes a period (.) the audit endpoint incorrectly reports a 404 Not Found response.

Example for user with ID my.user:

"GET /api/audit/roles/cucumber%3Auser%3Amy.user?limit=10" 404

However, periods in the ID work as expected for other Conjur endpoints:

"GET /api/roles/cucumber/user/my.user" 200

Also, encoding the period as %2E routes correctly, implying that the issue is the URL parsing:

"GET /api/audit/roles/cucumber%3Auser%3Amy%2Euser?limit=10" 200

Expected Outcome:

The audit API URL with the unencoded period returns the correct response code and data.