405 on DELETE Memento

[whikloj]

JIRA Ticket: https://fedora-repository.atlassian.net/browse/FCREPO-3824

What does this Pull Request do?

Changes response on DELETE to a Memento from 409 Conflict to 405 Method Not Allowed

How should this be tested?

Before PR create an object, then create a new version, then try to delete the version. Get:

> curl -i -ufedoraAdmin:fedoraAdmin http://localhost:8080/rest/test_version/00e7d1de-1758-4cb9-8044-6a762e8c2a14/fcr:versions/20220512161636 -XDELETE

HTTP/1.1 409 Conflict
Date: Thu, 12 May 2022 16:16:57 GMT
Set-Cookie: JSESSIONID=node01soir2ymob8vom0ew3290ysd283.node0; Path=/
Expires: Thu, 01 Jan 1970 00:00:00 GMT
Set-Cookie: rememberMe=deleteMe; Path=/; Max-Age=0; Expires=Wed, 11-May-2022 16:16:57 GMT; SameSite=lax
Link: <http://localhost:8080/static/constraints/ServerManagedTypeException.rdf>; rel="http://www.w3.org/ns/ldp#constrainedBy"
Content-Type: text/plain;charset=utf-8
Content-Length: 44
Server: Jetty(9.4.34.v20201102)

Path cannot contain a fcr: prefixed segment.

Pull in the PR and try again get

> curl -i -ufedoraAdmin:fedoraAdmin http://localhost:8080/rest/test_version/00e7d1de-1758-4cb9-8044-6a762e8c2a14/fcr:versions/20220512161636 -XDELETE

HTTP/1.1 405 Method Not Allowed
Set-Cookie: JSESSIONID=node0kjxaekpsi8yxs447ffmfkmu30.node0; Path=/
Set-Cookie: rememberMe=deleteMe; Path=/; Max-Age=0; Expires=Wed, 11-May-2022 16:37:32 GMT; SameSite=lax
Content-Length: 0
Server: Jetty(9.4.44.v20210927)

That is all.

Interested parties

@fcrepo/committers