Fix browsable API not supporting multipart/form-data correctly

Special case for when OneToOneField is also primary key.

Added FAQ section for funding site

Quote nested API parameters in api.js

I sometimes have parameter names with a period (.) in them, to represent nested objects, e.g. containerobj.inner_param. The Javascript was throwing an error in the browsable API when interacting with those parameters.

Use stacklevel=2 with DeprecationWarnings

This makes the warnings refer to the code where it is used, which makes
it easier to find and fix.

Added aria-label and a new region for accessibility purposes in base.html

Updated monthly report link + added Tom's PyCon talk

Navigating the page with a reader is easier is there is aria-label
and region.

https://www.w3.org/WAI/

Updated DjangoRestMulipleModel documentation to point to new repo loc…

import ordering matters

https://github.com/encode/django-rest-framework/issues/5135

Fix list_route, detail_route with kwargs contains curly bracket in url_path

Add `generator_class` parameter to `get_schema_view` docs.

Improve memory footprint when reading large JSON requests.

Added documentation from where to import get_schema_view

Fix exception when HTML_CUTOFF is set to None

make sure max_length is in FileField kwargs

Fixed test_hyperlinked_related_lookup_url_encoded_exists.

Space character ' ' is prohibited in IRIs, therefore we shouldn't
rely on encoding '%20' to ' ' in the HyperlinkedRelatedField tests.

- Autodetect missing boundary parameter for Content-Type header
- textarea value normalises EOL chars to \n when multipart/form-data requires \r\n

modified to use a reader since direct decoding is not supported

If pagination class, include the schema generation

https://github.com/encode/django-rest-framework/issues/5144

`get_schema_view` accepts `generator_class` parameter