Forward force_path_paste for non-composite test inputs

[afgane]

Problem

remote_to_input() passes force_path_paste to _get_path_or_location() on
its composite_data branch, but not on the branch immediately below it:

if composite_data := test_data["composite_data"]:
    tool_input["composite_data"] = [
        self._get_path_or_location(
            ...
            force_path_paste=force_path_paste,   # forwarded here
        ).path
        for fname_ in composite_data
    ]
else:
    path_or_location = self._get_path_or_location(
        fname,
        test_data,
        tool_id,
        tool_version=tool_version,               # ...but not here
        mode="file" if tool_input["class"].lower() == "file" else "directory",
    )

So galaxy-tool-test --force_path_paste has been silently ignored for ordinary
single-file inputs — the far commoner case — and those inputs fall through to
the client-upload path regardless of the flag.

Fix

Add the missing keyword argument.

Tests

There was no coverage of force_path_paste anywhere, so this adds two
parametrised tests in test/unit/tool_util/verify/test_interactor.py, one per
branch, since the bug is precisely that the two branches disagree. They record
what _get_path_or_location is called with rather than standing up an
interactor, as none of GalaxyInteractorApi.__init__'s connection setup is
relevant to argument forwarding.

Verified on Python 3.10 that the non-composite pair fails without the fix and
passes with it, while the composite pair passes either way.

[jmchilton]

It is conflicted and needs a rebase or merge - but it is ready to be merged after that.