Fixes for generic foreign key raw id widget

[mikebq]

I am porting a Django app to Django 1.11 and found some issues in the latest version of django-authority while doing so.

The class GenericForeignKeyRawIdWidget has ForeignKeyRawIdWidget as a base class but its __init__ method calls forms.TextInput.__init__(I am guessing that this is why its class name starts with the word "Generic"). The following PR is my attempt to address errors when attempting to view an individual permission from the permissions list view.

The first commit on this branch addresses an issue that occurs when render is called on this widget. During render a call is made to forms.TextInput.render which then calls self.get_context. Unfortunately this goes to ForeignKeyRawIdWidget.get_context which then blows up as it the instance of the class is missing members that would have been added by ForeignKeyRawIdWidget.__init__. In order to avoid this I have added a get_context which simply delegates to forms.TextInput.get_context (resolves up; but it is calling into something that has been initialised).

The second commit addresses an issue that occurs when clicking the anchor of class related-lookup from the rendered widget. In the app that I am porting from Django 1.6.11, using django-authority 0.10 to Django 1.11 using the latest version of django-authority there are differences in the form of the URL where the widget is rendered. With the old version of Django and Django-Authority the path of the URL is like this admin/authority/permission/21852/ where as with Django 1.11 and latest Django-Authority I am seeing admin/authority/permission/21852/change/. Thus having related_url hard coded to "../../../" is not going to work for both paths. What I have done is past the request object into the widget so that it can work out how many ../ it should use to get back to the root of the "related" path.

If you think this PR is off course or wrong could you please let me know :) thank you.

[codecov]

Codecov Report

✅ All modified and coverable lines are covered by tests.
✅ Project coverage is 43.64%. Comparing base (3677b42) to head (be36893).
⚠️ Report is 15 commits behind head on master.

Additional details and impacted files

@@            Coverage Diff             @@
##           master      #69      +/-   ##
==========================================
+ Coverage   39.00%   43.64%   +4.64%     
==========================================
  Files           7        7              
  Lines         423      433      +10     
  Branches       78       79       +1     
==========================================
+ Hits          165      189      +24     
+ Misses        250      233      -17     
- Partials        8       11       +3     

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

🚀 New features to boost your workflow:

• ❄️ Test Analytics: Detect flaky tests, report on failures, and find test suite problems.

[mikebq]

I added this as running tox locally would fail for py37-dj22 and report the following:

======================================================================
ERROR: test_raw_id_GenericForeignKey (authority.tests.PermissionAdminForDBFieldTests)
----------------------------------------------------------------------
Traceback (most recent call last):
  File "/Users/bia/django-authority/example/../authority/tests.py", line 490, in test_raw_id_GenericForeignKey
    raw_id_fields=['object_id'])
  File "/Users/bia/django-authority/example/../authority/tests.py", line 479, in assertFormfield
    ff = ma.formfield_for_dbfield(model._meta.get_field(fieldname), request=None)
  File "/Users/bia/django-authority/example/../authority/admin.py", line 154, in formfield_for_dbfield
    for f in self.model._meta.virtual_fields
AttributeError: 'Options' object has no attribute 'virtual_fields'

Seems that virtual_fields were deprecated in Django 1.10 and that 2.2 only has private_fields https://docs.djangoproject.com/en/2.2/_modules/django/db/models/options/