The settings registry's template functions (setting_id, settings_rows and settings_page_for_path) are now registered by TwigRenderer::addSettingsRegistryFunctions(). Tests that render settings pages call it instead of copying these functions. One copy had already drifted: it accepted ids the registry does not declare and left out data-setting. A test that renders a settings page now fails if the page uses an undeclared id, and a test can no longer break just because a settings page starts using one of these functions. Internal change; nothing changes for members.
Page tests use the real settings registry functions
Tests that render a settings page now use the same setting_id, settings_rows and settings_page_for_path as the site, instead of their own copies.