Map config delete broken in NodeJS legacy API v1

[sweco-semara]

Describe the bug
Map configuration cannot be deleted with NodeJS back-end using API v1.

Since #1309 and the introduction of OpenAPI specifications, commit 48a4c8a cleans up v2 API-introduced HTTP PUT and HTTP DELETE but accidentally also removes the HTTP GET legacy method. Resulting state is that NodeJS back-end API v1 cannot delete map configurations at all.

To Reproduce
Steps to reproduce the behavior:

1. Set up a Hajk installation with NodeJS back-end
2. Configure Hajk admin config.json mapsettings.url_map_delete = "/api/v1/mapconfig/delete"
3. Use admin to create a new map config
4. Try to delete the new map config
5. Back-end always returns HTTP/404 not found on the GET to /api/v1/mapconfig/delete/:name

Expected behavior
Expect step 5 result: backend service delegates request to Express router apis\v1\controllers\mapconfig\router.js which in turns map the calls to the ConfigService/config.service.js deleteMap() method.

[sweco-semara]

Seems the HTTP method clean-up from OpenAPI spec v1 in 48a4c8a accidentally left the HTTP PUT for mapconfig create endpoint but instead removed HTTP GET for mapconfig delete. Fix is a minor adjust of the OpenAPI spec YAML. Also the v1 router can be cleaned from non-existing v2 new HTTP verbs now that the separation of routers is completed.