Adding new index
Quit getType index and column definitions
Fix AR copy_to_new: Form values incorrectly set
Cleanup resolved_values in ar_add form handler
"Copy to new" added in base AnalysisRequests view

This means that all subclasses and views which add the copy_to_new
custom_action into bika_listing views, need to stop doing that.

The button is shown if the user has 'BIKA: Manage Analysis Requests' or
'Modify portal content' permission on current context.
Add copy_to_new to BatchBook view's transitions
LIMS-1414 In BikaSetup/Instruments, after done a click to sort by type, the list disappear.
Merge branch 'issue/1414' into hotfix/next
Fix #LIMS-1374 Auto label printing does not happen for an AR drop-down receive
Add ResultsRange field to AnalysisRequest

The field setter accepts specs for a set of analyses.  It creates
the ResultsRange value from different places, in the following order:

    1 - Client specs with spec.SampleType match
    2 - Lab specs with spec.SampleType match
    3 - Take override values from AR.Specification field
    4 - Take override values from form or jsonapi

The field value is stored as a list of dictionaries.
aranalysesfield sets spec to AR.

The code to set analysis.specification is removed.
Modify AR Add submit handler to provide keyword

keyword is used to set the AR spec, where before, these values were
just written to the analysis, and this info was not required.
analyses listings retrieve specs from AR, not analysees
AnalysisSpec.SampleType instead of title matching

There was some silly code that matched sampletype-title with spec-title
to set defaults, which is removed.
add dicts_to_dict to utils

makes it easier to work with lists of dicts
ResultOutOfRange check for normal analyses uses AR value
Remove unused code
LIMS-1425 Verify Workflow (bika_listing) recursion
LIMS-1425 Verify Workflow (bika_listing) recursion
Merge branch 'hotfix/next' into next-arspecs