Usernames in Team Calendar's restrictions are not case insensitive

By default, Confluence treats both usernames test and TEST the same. However, restriction checking on usernames in Team Calendars is not case insensitive. Usernames test and TEST are treated different by Team Calendars.

This proves to be a problem when Confluence content indexing is corrupted/not updated, because Team Calendars acquires user names from auto-complete widget, which is based on index. For example, assume the following scenario:

1. Username in the index: USER1. Username in cwd_user table is: user1
2. A user applies an edit restriction on a calendar for USER1
   • Team Calendars saves the information in the database, specifically in the BANDANA table (_edit_events_users_ key):

     <set>
       <string>USER1</string>
     </set>

3. When USER1 tries to edit, it is not able to edit the calendar because of the difference in casing
4. Updating the record in the database from USER1 to user1 fixed the issue

Conclusion: Team Calendars should behave the same way as Confluence when it comes to restriction checking. Usernames with different casing should be treated the same.