Persists if a board list is collapsed for each user.

It adds  a hash response which includes
the count, success state and the moved
issues itself so the caller has additional
information about the result of the
process.

Add specs for new endpoint to move multiple issues.
Add changelog entry

Just check the first issue for the ability to move / update

Add specs for exceeding limits and malformed requests

Changed name of shared examples

Change title of changelog entry

Use %i instead of %w

Check permission to update issue on project instead of board

Use admin_issue permission to check for issue move ability

Changed variable name to avoid shadow issue_params method

Rename route to bulk_move

Change route definition

Check permissions for each issue

Combine methods for parameters permit check

Remove extra context

Change description of context

Check param for type Array

Add unit tests to MoveService

Use before_action for permission check

Use set instead of let!

Use let's instead of set

Refactor code to allow multiple issue boards management for projects
in CE

to support manual sorting on the frontend

This style change enforces `return if ...` instead of
`return nil if ...` to save maintainers a few minor review points

Adds additional count param to Boards::Visits::LatestService

Signed-off-by: Rémy Coutable <remy@rymai.me>