Prevent library-specific default configurations from being overridden when a new default library is saved

Problem/Motivation

Currently, when more than one Charts submodule (e.g. Highcharts) is saved, users should select which library is the default in the "Chart configuration" page (/admin/config/content/charts). This adds a horizontal tab on that page with additional settings that are specific to that library. In the case of Highcharts, that includes language options like what a thousands separator should be.

If a user decides to switch which library is the default, then those settings are lost. I happen to do this a lot in order to see how each of the libraries looks on the page generated by the Charts API Example module (/charts/example/display). This can be extremely frustrating, especially now that the Highcharts module has settings for additional libraries that can be included.

Steps to reproduce

1. Enable the Highcharts and Chart.js modules.
2. Navigate to /admin/config/content/chart
3. Set Highcharts as the default library, then check "Enable Highcharts' "Accessibility" library" in the "Highcharts settings" horizontal tab.
4. Save.
5. Set Chart.js as the default library.
6. Save.
7. Set Highcharts as the default library and check the "Highcharts settings" horizontal tab: the Accessibility library will be unchecked.

Proposed resolution

When a new Charts submodule is enabled, it should have its own horizontal tab (it shouldn't be dependent on the default library).

Remaining tasks

User interface changes

API changes

Data model changes