Add DB indexing to fields like Analyses status.

[sambles]

Issue Description

Django supports putting db_index=True on model fields, this can speed up DB level fetch requests:

types-of-database-indexing-in-django
https://docs.djangoproject.com/en/5.1/ref/models/indexes/

[sambles]

SubTask Status

OasisPlatform/src/server/oasisapi/analyses/models.py

Lines 168 to 169 in 8f6e3a6

	status = models.CharField(max_length=max(len(c) for c in status_choices._db_values),
	choices=status_choices, default=status_choices.NEW, editable=False)

analysis.status

OasisPlatform/src/server/oasisapi/analyses/models.py

Lines 92 to 97 in 8f6e3a6

	status = models.CharField(
	max_length=max(len(c) for c in status_choices._db_values),
	choices=status_choices,
	default=status_choices.PENDING,
	editable=False,
	)

[sambles]

Amir: For tables that have group_id in them, I think it also makes sense to have index on group_id, if group_id points to a group of users that belong to a separate security group/organisations. I think group_id index will help finding resources belonging to that group quicker.

Not 100% sure about this but if there is any field that a list query sorts the result based on that, I think indexing on that field might be beneficial. Also any parameter that list endpoints accept as filter parameters could be helpful. But I guess it’s too many index additions it’s better to do it in stages. Because indices consume additional storage in the DB so there might be a considerable storage impact if too many things are indexed.