fix(filemanager): sequencer ordering

[mmalenic]

Closes #395

Changes

• Order by sequencer in list API queries.
• Add an index on the sequencer to support better sorting of ingested events.
  • I think this effectively does what this piece of code is doing, except it's a native construct to the database:

    orcabus/lib/workload/stateless/stacks/filemanager/database/queries/ingester/aws/update_reordered_for_created.sql

    Lines 64 to 90 in 2e4772c

    	-- And filter them to the objects that need to be updated.
    	objects_to_update as (
    	select
    	*
    	from current_objects
    	where
    	-- Check the sequencer condition. We only update if there is a created
    	-- sequencer that is closer to the deleted sequencer.
    	current_objects.deleted_sequencer > current_objects.input_created_sequencer and
    	(
    	-- Updating a null sequencer doesn't cause the event to be reprocessed.
    	current_objects.sequencer is null or
    	-- If a sequencer already exists this event should be reprocessed because this
    	-- sequencer could belong to another object.
    	current_objects.sequencer < current_objects.input_created_sequencer
    	) and
    	-- And there should not be any objects with a created sequencer that is the same as the input created
    	-- sequencer because this is a duplicate event that would cause a constraint error in the update.
    	current_objects.input_created_sequencer not in (
    	select sequencer from current_objects where sequencer is not null
    	)
    	-- Only one event entry should be updated, and that entry must be the one with the
    	-- deleted sequencer that is minimum, i.e. closest to the created sequencer which
    	-- is going to be inserted.
    	order by current_objects.deleted_sequencer asc
    	limit 1
    	),

    This is one of the reasons why I simplified the database ingestion, because I think a similar trade off with ingest/query performance can be achieved by just using an index (although I would need to test this to be sure).

[brainstorm]

🚀