As you explained, there are two possible solutions.
Forcing the use of django-debug-toolbar 1.9.0 works, if also Django==1.10.7 is used. This is the list of packets from pip freeze that make the migration script work. working_list_of_packages.txt
Fix the problem taking into account the two possible versions of Django and the django-debug-toolbar. In progress...
And it rises after the first migration operation in line 37
This relation is an index in the table study_subject that I think, should be called web_stydysubject... instead of web_subject...
My experience with migrations is limited, but, would be enough to change the index name before creating the new model?
Either way... I don’t know it tries to create a new index and why it conflicts if it’s going to be on a different table (web_subject).