HistoricOneToOneField

[JordanHyatt]

Adds support for HistoricOneToOneField

Description

Implemented the solution proposed by @quadracik in issue #1031

Related Issue

This PR addresses issue #1031 and #1389

Motivation and Context

How Has This Been Tested?

Appropriate unit tests have been written and follow the ones written for HistoricForeignKey

Types of changes

• Bug fix (non-breaking change which fixes an issue)
• New feature (non-breaking change which adds functionality)
• Breaking change (fix or feature that would cause existing functionality to change)

Checklist:

• I have run the pre-commit run command to format and lint.
• My change requires a change to the documentation.
• I have updated the documentation accordingly.
• I have read the CONTRIBUTING document.
• I have added tests to cover my changes.
• I have added my name and/or github handle to AUTHORS.rst
• I have added my change to CHANGES.rst
• All new and existing tests passed.