Inconsistent links in collections resources when api-key given

[teezip]

Inconsistent links in collections resources when api-key given

[jampukka]

This is an oversight from when the f query parameter was added to /collections/{collectionId/items. Currently the code creates one /items link and one /items?f={outputformat} for each available outputformat. (https://github.com/nlsfi/hakunapi/blob/main/src/hakunapi-simple-servlet-javax/src/main/java/fi/nls/hakunapi/simple/servlet/javax/operation/CollectionMetadataUtil.java#L31-L36) (link is to current main branch, bound to be out-dated in the future).

Adding the api-key (or other allowed query parameters) to the plain /items links is an easy fix.

[jampukka]

This is also somewhat related to #25 and #18. Should we create separate links with f-parameter throughout the API or drop them all together? f-parameter is little different between /collections/{collectionId}/items[/{featureId}] and other endpoints as they only support JSON/HTML whereas /items might include geopackage, csv etc.

[teezip]

For services supporting HTML browsing experience maybe the f-parameter should be implemented throughout the API to make it easier for demo purposes as discussed earlier.