Store data in database rather than config

Problem/Motivation

Whenever new content is added this module adds data in the thrid_party_settings of the content type. If the config is managed by a version control system then the config will need to be committed _every time new content is created_. I would argue that this data should be considered as content, rather than config, and stored in the database instead.

Steps to reproduce

1. Create a new entity (node, taxonomy term, etc)
2. Export config
3. Note that the config has been changed to include data concerning the new entity

Proposed resolution

Create a custom database table
Store and access Entity Redirect data in this custom database table

Remaining tasks

User interface changes

N/A

API changes

TBC

Data model changes

TBC