Upgrade path is broken

Problem/Motivation

After upgrading from 1.8.0 to 2.0.9 the google tag works differently from before.

Previously, debugging with the GA debug extension gave an order of :

Processing GTAG command: ["consent", "default"..
Processing data layer push: {drupalLanguage: "en", (values filled)...
Processing data layer push: {event: "gtm.init_consent", gtm.uniqueEventId: 2}
Processing data layer push: {event: "gtm.init", gtm.uniqueEventId: 3}
Processing GTAG command: ["config", "
..

For comparison, after the upgrade:

Processing GTAG command: ["consent", "default"
Processing data layer push: {event: "gtm.init_consent", gtm.uniqueEventId: 2}
Processing data layer push: {event: "gtm.init", gtm.uniqueEventId: 3}
Processing GTAG command: ["config", "... (parameters not set)
Processing GTAG command: ["js",
Processing GTAG command: ["set", "developer_id...
Processing data layer push: {gtm.start: 1787301694797, event: "gtm.js", gtm.uniqueEventId: 26}
Processing data layer push: {drupalLanguage: "en", (values filled)...

Steps to reproduce

IDK - since this is a complex setup with a server side container and custom parameters being deferred from Drupal datalayer values

Proposed resolution

Looking at the issue queue, this should come with a warning that the upgrade path can be broken.

I wonder also, would it not be easier to make the 1.x version compatible with Drupal 11?

Remaining tasks

User interface changes

API changes

Data model changes