Fix Django deprecation warnings #578
                
     Merged
            
            
          
  Add this suggestion to a batch that can be applied as a single commit.
  This suggestion is invalid because no changes were made to the code.
  Suggestions cannot be applied while the pull request is closed.
  Suggestions cannot be applied while viewing a subset of changes.
  Only one suggestion per line can be applied in a batch.
  Add this suggestion to a batch that can be applied as a single commit.
  Applying suggestions on deleted lines is not supported.
  You must change the existing code in this line in order to create a valid suggestion.
  Outdated suggestions cannot be applied.
  This suggestion has been applied or marked resolved.
  Suggestions cannot be applied from pending reviews.
  Suggestions cannot be applied on multi-line comments.
  Suggestions cannot be applied while the pull request is queued to merge.
  Suggestion cannot be applied right now. Please check back later.
  
    
  
    
PR fixes Django deprecation warnings.
This PR does not fix all deprecation warnings, as the rest of the deprecation warnings are coming out from external libraries we use, i.e:
Ideally, once we bump Django, we would want to upgrade these modules as well.
One that made my head spin a little was the following:
Though I tried ordering the Queryset, I am not fully sure where this is coming from.