Refactor: use restInfo handler directly in output-geoservice

[rgwozdz]

This PR is start of effort to let output-geoservices plugin do its own routing (as opposed to the FeatureServer route.js module). This effort is a pre-cursor to support an applyEdits endpoint.

[changeset-bot[bot]]

⚠️ No Changeset found

Latest commit: 55b9559fe31ad24b8a625a7b4c504f12cd7cbd7b

Merging this PR will not cause a version bump for any packages. If these changes should not result in a new version, you're good to go. If these changes should result in a version bump, you need to add a changeset.

This PR includes no changesets

When changesets are added to this PR, you'll see the packages that this PR includes changesets for and the associated semver types

Click here to learn what changesets are, and how to add one.

Click here if you're a maintainer who wants to add a changeset to this PR

[github-actions[bot]]

Coverage Report (change vs master)

File Path	Statements	Branches	Functions	Lines
packages/featureserver/src/rest-info-route-handler.js	100.0 vs 100.0	100.0 vs 100.0	100.0 vs 100.0	100.0 vs 100.0
packages/featureserver/src/route.js	85.5 vs 85.7	76.5 vs 76.5	100.0 vs 100.0	85.5 vs 85.7
packages/featureserver/src/helpers/combine-body-query-params.js	100.0 vs (NA)	100.0 vs (NA)	100.0 vs (NA)	100.0 vs (NA)
packages/featureserver/src/helpers/index.js	100.0 vs 100.0	100.0 vs 100.0	100.0 vs 100.0	100.0 vs 100.0
packages/featureserver/src/helpers/normalize-request-params.js	100.0 vs 100.0	100.0 vs 100.0	100.0 vs 100.0	100.0 vs 100.0
packages/output-geoservices/src/index.js	100.0 vs 100.0	100.0 vs 100.0	100.0 vs 100.0	100.0 vs 100.0