Align integration to work with self-service for premium features.

[Mati365]

Suggested merge commit message (convention)

Feature: Align integration to work with self-service for premium features.

---

Additional information

More details: ckeditor/ckeditor5#17317

[coveralls]

Pull Request Test Coverage Report for Build 80309925-b790-4fc6-ae21-adaf81440a58

Details

• 6 of 6 (100.0%) changed or added relevant lines in 3 files are covered.
• No unchanged relevant lines lost coverage.
• Overall coverage remained the same at 100.0%

---

Totals
Change from base Build e62939bb-7648-41a5-a87b-f8d6d81de556:	0.0%
Covered Lines:	164
Relevant Lines:	164

---

💛 - Coveralls

[psmyrek]

Script for preparing the release (yarn release:prepare-packages) modifies one file outside the release directory:

$ git status
On branch editor-integration/angular/add-usage-data
Your branch is up to date with 'origin/editor-integration/angular/add-usage-data'.

Changes not staged for commit:
  (use "git add <file>..." to update what will be committed)
  (use "git restore <file>..." to discard changes in working directory)
        modified:   src/ckeditor/package.json

no changes added to commit (use "git add" and/or "git commit -a")

Also, in the generated release directory, there are two package.json files:

• release/ckeditor5-angular/package.json
• release/ckeditor5-angular/esm2022/package.json

Is it expected?

[Mati365]

@psmyrek 🤔 I'll check that.

edit: You are right, that esm2022/package.json file should not be there, I'll fix that.

[Mati365]

@psmyrek This package.json was used by ESM import to determine version of integration. You are correct, we can get rid of it, as it may be problematic in older installations. I updated the release script, as it's quite hard to import environment files without compiler changes, and replaced the version during the release process. It minimizes amount of changes in deployment flow. Can you take a look again?

[psmyrek]

LGTM 🎉