Parameterize path after regex validation failure

What does this MR do and why?

Allows paths that validate against our oci_repository_path_regex to be used when importing projects with direct transfer.

This means that valid paths, such as php.ms-evenements.brakeman are not changed to php-ms-evenements-brakeman

MR acceptance checklist

Please evaluate this MR against the MR acceptance checklist. It helps you analyze changes to reduce risks in quality, performance, reliability, security, and maintainability.

Screenshots or screen recordings

Screenshots are required for UI changes, and strongly recommended for all other merge requests.

Before

After

How to set up and validate locally

Numbered steps to set up and validate the change are strongly suggested.

1. On the source instance, in a group you are able to import, create a project with the following name: php.ms-evenements.brakeman (note the dots)
2. Import the group (with projects) using Direct Transfer: New Group > Import Group > Import groups by direct transfer. You will need an access token for the destination instance that has repo scope.
3. Alternatively you can use the /bulk_imports api: https://docs.gitlab.com/ee/api/bulk_imports.html#start-a-new-group-or-project-migration
4. Once the group/project is imported on the destination instance, note no change in the project's URL path: testing-group/php.ms-evenements.brakeman

Related to #455888 (closed)