I still think we'll have many cases where we will have configured the SSO and some people will have signed in before the institution is able to do a CSV import of all users, so the use case remains valid. I think we need the following workflow:

1. Does the user with the provided login id already exist?
2. If not, create the user with the provided details
3. If so, do the following:

3a: If the display name of the user is the same as its login id and a real name is provided in the CSV, update the display name to the provided value
3b: If the user does not have an email address and an email address is provided in the CSV, update the email address to the provided value

4. If `forceProfileUpdate` has been provided, update the display name and email address regardless, at least if the CSV values are different than the ones that are already there