Solution detail page and a single LinkResolver

Closes two annex items that turned out to be the same defect seen from two
sides: markets could link to a detail page, solutions could not, and the code
that turns a page uid into a URL existed four times over.

detail_page for Solution (B-11)
- ext_tables.sql, TCA (group on pages, maxitems 1, in showitem behind slug)
  and Domain\Model\Solution mirror the Market field exactly
- SolutionShowJsonRenderer emits detailUrl
- ModelcardJsonRenderer serialized no detailUrl at all: its shared
  market|solution branch never carried the field. Market modelcards therefore
  gain a link here too, not just solutions.

Service\LinkResolver (B-12)
- one implementation replaces four private copies (Market list/show, Usecase
  list/show). The copies had drifted: Market returned null on failure, Usecase
  an empty string. The contract is now explicit -- null means "no link".
- Usecase keeps a thin resolvePageUrl() wrapper appending ?? '', because it
  concatenates paths and a null would tear the strings apart.
- LocationsJsonRenderer and NewsJsonRenderer stay out on purpose: they resolve
  a full parameter construct resp. slug paths plus canonical, which is not
  page-uid-to-URL and does not fit the same contract.

Requires on the server, the column exists in code only:
    vendor/bin/typo3 database:updateschema "*.add,*.change"
    vendor/bin/typo3 cache:flush

packages/vitec/ext_tables.sql

@@ -155,6 +155,7 @@ CREATE TABLE tx_vitec_domain_model_solution (
     l10n_diffsource mediumblob,
     title varchar(255) DEFAULT '' NOT NULL,
     slug varchar(255) DEFAULT '' NOT NULL,
+    detail_page int(11) DEFAULT '0' NOT NULL,
     subtitle varchar(255) DEFAULT '' NOT NULL,
     teaser varchar(255) DEFAULT '' NOT NULL,
     description text,