Rename the action-setfield widget to action-setfields

It makes more sense, and allows us to add a widget: `<$action-setfield
$tiddler=“title” $name=“fieldname” $value=“fieldvalue”/>`
Add action-setfield widget
Add action-deletetiddler widget
Simplify action-setfield widget
Add input box for new field value to edit template
Use action-deletefield widget in edit template fields editor

On the way to deprecating the field mangler widget
Fix docs typos

Thanks @Evolena
Merge action-setfield and action-setfields widgets

Less confusion, hopefully.
Fix typo in action-setfield widget
Extend search filter to allow field to be specified
Update advanced search standard to use search tabs

We reuse the tabs introduced for the sidebar search results
Provisionally extend search results to list title matches separately

I’m not sure whether this is a good solution. Nor am I keen on the
horizontal rule to separate the two groups of results.
Default tiddler info to the fields tab
tagmanager info heading
Merge pull request #1065 from pmario/german-translations

tagmanager info heading
Improve the format of widget message parameters

In 5.1.3 we introduced the idea that the `event.param` variable could
optionally be a hashmap, allowing multiple values to be passed with the
message.

This change moves the hashmap to a separate `event.paramObject`
variable, allowing us to pass both a hashmap and a param string.
Update new tiddler message handling to accept title and fields

Now you can create a new tiddler with both a template and additional
specified fields.
Update modal handling to allow variables to be passed

@felixhayashi I’m afraid I haven’t used your pull request as there were
a few details that I wanted to do differently. The main change is that
these changes allow both a param string and hashmap to be specified.
Release note update
Release note update