Support for Student IDs

[eriq-augustine]

We currently identify users by email, name, LMS ID, or label.
It could be nice to identify them by student ID as well.
Some LMSs may already collect this data in extra_fields.

This would slightly change the label semantics, since we can probably use either LMS id or student id.
We may have to generalize query semantics more to handle more IDs.
As long as it is sufficient to uniquely identify users at resolve time, it should be sufficient.

This blocks #13.

[XxSURYANSHxX]

Hey @eriq-augustine, this is my proposed approch on implementing support for student ids. please have a look and if you approve ill make a PR ASAP. Thankyou

1. I will Add student_id field to User Model
   File: lms/model/users.py

What I'll do: Add student_id as a new parameter in the ServerUser class, just like email and name.

2. I will Update UserQuery to include student_id
   File: lms/model/users.py
   What I'll do: Make sure queries can include student IDs when matching users.

3. Extend BaseQuery to handle Student IDs
   File: lms/model/query.py

What I'll do:
Update matching logic to compare student IDs
Update string format to show student IDs in brackets: [student_id]
Update parsing to recognize patterns like "Name [12345] (67890)"

4. Extract Student ID from Canvas API
   File: lms/backend/canvas/model.py

What I'll do: Extract the sis_user_id field from Canvas API responses and store it as student_id.

5. Add Tests
   What I'll do: Write tests to make sure student ID queries work correctly.

i do have some Questions if you can clarify.

1. Should student IDs be shown in output by default?
2. If someone enters just a number, should we assume it's LMS ID or student ID?
3. Any other edge cases I should consider?

[eriq-augustine]

That generally sounds fine.

1. Should student IDs be shown in output by default?

This question does not really make sense with what you have above.
I recommend thinking more about this in the context of the model classes.

2. If someone enters just a number, should we assume it's LMS ID or student ID?

As long as we can uniquely identify a user, it should not matter.
We can let it be either.

3. Any other edge cases I should consider?

There are several cases, especially around the parsing of queries, but they are mostly implementation dependent so it will have to wait until you have something to start with.

[XxSURYANSHxX]

thanks for the go ahead @eriq-augustine, i will create a PR and please let me know your review and feedback. Thankyou

[XxSURYANSHxX]

@eriq-augustine i have created the PR #31, Please have a look