…utePartHandler

The api will be

```
public function uriFor(NodeAddress $nodeAddress, Options $options = null): UriInterface
```

the custom options will likely be unintended as `uriFor` uses preview uris for non-live uris.
Such preview route will likely not exist, and thus it will just provoke hard to debug errors.

- Use flows base uri if configured for sub dir installations
- Pass `uriPathPrefix` correctly along when base uri is configured
- support for `FLOW_REWRITEURLS === ß` is not planned as this option is to be removed

…iBuilding

… uri

…ng options

see neos/flow-development-collection#3354

…iBuilding

…uilding uris from Fusion or Fluid

The magic of keeping the format either has helped (by knowing it beforehand) or worse lead to confusion and hard to debug uri building errors (the `@format: json` part in the exception dump tends to go unnoticed for the untrained eye)

Still for this change it would be cruel to change behaviour like this so we reimplement it.

The filter like signatures dont feel quite right because they only have one argument ... and its a yagni to add new args