LIMS-1683: Show buttons for next/previous container on plate view

[ndg63276]

JIRA ticket: LIMS-1683

Summary:

#912 added buttons to move to the next/previous container in the puck view, this PR is to add the same buttons to the plate views.

Changes:

• Move scoped CSS for the header row and the flat buttons into the general use area
• Add prev/next buttons to the view both of plates that have been imaged and those that haven't
• Add code to get sibling containers, work out the current container number, and which container ids are next/previous, to add titles to the buttons, and disable when necessary
• Always do the container sorting in the backend for consistency, and use container id to distinguish containers with the same name
• Remove unused function updateContainerSampleGroupsData and related functions fetchDewars and fetchContainers and related variable containersCollection.

To test:

• Go to a puck with siblings (eg /containers/cid/367188), check the Next and Prev Container buttons still appear, look the same as on prod, have titles when you hover, and disable correctly when on the first / last puck of the dewar.
• Go to a plate that has been imaged (eg /containers/cid/373688), check the Next and Prev Container buttons appear and behave the same as for pucks
• Go to (or create) a plate that has not been imaged (eg /containers/cid/373685), check the Next and Prev Container buttons appear and behave the same as for pucks
• Add a puck and a plate to a dewar with an already imaged plate, check you can move between the 3 kinds as expected

[gfrn]

Nitpick, but could result be initialised like

let result = new Containers(null, { state: { pageSize: 9999 } });?

[gfrn]

Suggested change

	@apply tw-bg-red-700
	@apply tw-bg-red-700;

[gfrn]

Should this come after foundCurrent is set? (line 779)

As it currently is, it might just not reflect the actual condition because it is evaluated before the containerId check is executed

[ndg63276]

No, this is deliberate. You are looping through all the containers (in order), so you need to have already found the currently-displayed one, (and not yet set the 'next' one), in order to set this container as the 'next' one.

[gfrn]

Yeah, that makes sense, I'll approve it now, thanks for having a look!