#206: default parcel page sorting

[kaydentsoftwire]

What's changed

Added secondary sorting to sort methods in this order: packing date > packing slot > deliveries then collections > collection centre name > postcode

(if one of these is the primary sort then this is moved to the top).

For each column:

• Family category = family category > packing date > packing slot > delivery/collection > collection centre name > postcode
• Full name = full name > packing date > packing slot > delivery/collection > collection centre name > postcode
• Postcode = postcode > packing date > packing slot > delivery/collection > collection centre name
• Phone number = phone number > packing date > packing slot > delivery / collection > collection centre name > postcode
• Voucher number = voucher number > packing date > packing slot > delivery / collection > collection centre name > postcode
• Packing slot = packing slot > packing date > delivery / collection > collection centre name > postcode
• Method = method > collection centre name > packing date > packing slot > postcode
• Last status = last status > packing date > packing slot > delivery / collection > collection centre name > postcode
• Created at = created at > packing date > packing slot > delivery / collection > collection centre name > postcode

The final sort for all columns is parcel id to ensure consistency

Screenshots / Videos

Before	After

Checklist

• [x] The ticket is up-to-date - Please document any deviations from the original approach if there is any.
• [x] I have documented the testing steps for QA
• [x] I have self-reviewed this PR
• [x] Make sure you've verified it works via npm run dev
• [x] Make sure you've verified it works via npm run build and npm run start
• [x] Make sure you've fixed all linting problems with npm run lint_fix
• [x] Make sure you've tested via npm run test:e2e

[AmeliaIsCoding]

Hi @kaydentsoftwire - just checking that you've merged with dev recently, as in my recent ticket I included sorting by "client_is_active" before sorting by any client information fields - this is required because if a client is inactive but has personal information (i.e., a seeded inactive client), we could expose the sensitive information by sorting. This should be included in these sorts now please :)

client information fields are anything in the backend clients table (eg postcode)

[stonelink]

The defaultParcelsSortConfig and changes are to fix the dividing lines behaviour - see this comment: https://github.com/NorwoodAndBrixtonFoodbank/nbf-website/issues/152#issuecomment-2154830486