Django-oscar

- Add ``order`` as a value for the ``CARD_REJECT_ERROR`` string template literal.

- Use Cybersource's ``reason_code`` field in addition to the ``decision`` field when deciding how to handle a response.
- Move secure acceptance profile data into the database.
- Profiles can be configured in the Django Admin interface. A default profile is created when running migrations based on the old environment variable settings.
- Stores the profile secret key in the using Fernet encryption via `django-fernet-fields <https://django-fernet-fields.readthedocs.io/en/latest/>`_. Therefore, you should declare a ``FERNET_KEYS`` setting in your project.
- Since secure acceptable profiles are limited to a single domains for customer redirect pages, this change allows a single Django instance to serve multiple domains (by using multiple profiles).

- Fix Django 2.0 Deprecation warnings.

- Make it possible to use a placeholder (``{order_number}``) in ``settings.CARD_REJECT_ERROR``.

- Add better error handling to the Cybersource response view. Prevents exceptions when a customer refreshes and resends one of the payment POST requests.

- Adds an order's shipping method into calls to Cybersource. This field can then be used by decision manager to help make decision regarding order fraud.
- Cybersource expects to receive one of the following values:
- `sameday`: courier or same-day service
- `oneday`: next day or overnight service
- `twoday`: two-day service
- `threeday`: three-day service
- `lowcost`: lowest-cost service
- `pickup`: store pick-up
- `other`: other shipping method
- `none`: no shipping method
- You can configure the mapping of Oscar shipping method code to Cybersource shipping method codes using the ``CYBERSOURCE_SHIPPING_METHOD_DEFAULT`` and ``CYBERSOURCE_SHIPPING_METHOD_MAPPING`` Django settings.
- Added exception handling and logging for bug sometimes occurring in the Cybersource reply handler.