[ID-741]Fix Case-Insensitive Sorting

[stefanvit]

Description

Fix Case-Insensitive Sorting

**Resolves #741

Review Time Estimate

• Immediately
• Within a week
• When possible

Type of changes

• Bug fix (non-breaking change which fixes an issue).
• New feature (non-breaking change which adds functionality).
• Breaking change (fix or feature that would cause existing functionality to not work as expected).
• Other (any another change that does not fall in one of the above categories.)

Checklist:

• [x ] I have signed the Rokwire Contributor License Agreement (CLA). (Any contributor who is not an employee of the University of Illinois whose official duties include contributing to the Rokwire software, or who is not paid by the Rokwire project, needs to sign the CLA before their contribution can be accepted.)
• I have updated the CHANGELOG.
• I have read the Contributor Guidelines.
• I have performed a self-review of my own code.
• I have commented my code, particularly in hard-to-understand areas.
• My change requires updating the documentation.
• I have made necessary changes to the documentation.
• I have added tests related to my changes.
• My changes generate no new warnings.
• New and existing unit tests pass locally with my changes.
• Any dependent changes have been merged and published in downstream modules.

[petyos]

It does not fix sorting as sorting is applied here:

Stephen said, can you add a case insensitivity flag to the Core BB, applied to the Mongo query. He passed me this:

Directory Sort that needs case insensitivity applied

core-building-block/driven/storage/adapter.go

Line 1544 in 01e7e72

pipeline = append(pipeline, bson.M{"$sort": bson.D{{Key: "profile.last_name", Value: 1}, {Key: "profile.first_name", Value: 1}}})

[stefanvit]

Hi @petyos
Normalization ($addFields):
Before sorting, the fields profile.last_name and profile.first_name are temporarily converted to lowercase and stored as normalized_last_name and normalized_first_name.
Sorting ($sort):

The documents are then sorted using the normalized fields.
The original fields (profile.last_name and profile.first_name) remain unchanged in the documents.
Pipeline Progression:

These normalized fields exist only temporarily in the pipeline and won't appear in the final output unless explicitly included in a $project stage.

[petyos]

LGTM