Enhancement/6041 add incompatible plugins backend

[mostafa-hisham]

Description

Plugin part for add incompatible plugins in backend

Fixes #6041

Type of change

• Enhancement (non-breaking change which improves an existing functionality)

Is the solution different from the one proposed during the grooming?

No

How Has This Been Tested?

• Locally
• Unit test

Checklist:

• My code follows the style guidelines of this project
• I have performed a self-review of my own code
• I have commented my code, particularly in hard-to-understand areas
• My changes generate no new warnings
• I have added tests that prove my fix is effective or that my feature works
• New and existing unit tests pass locally with my changes

[Mai-Saad]

@mostafa-hisham Thanks for the PR. During the exploratory test can see that the transient wpr_dynamic_lists_incompatible_plugins is not deleted after deleting WPR. Can you please check that?

Notes:

• As per discussion, we need to add data to the live backend before the release so it grabs the correct list.
• Currently the wpr_dynamic_lists_incompatible_plugins.json, is not in the WPR folder with installation. As per discussion, the new list file will be created after creating a new release on GitHub

[mostafa-hisham]

@mostafa-hisham Thanks for the PR. During the exploratory test can see that the transient wpr_dynamic_lists_incompatible_plugins is not deleted after deleting WPR. Can you please check that?

@Mai-Saad
should be fixed now

[engahmeds3ed]

Good job, minor changes.

[Tabrisrp]

We could use the Options_Data class here by passing it to the constructor of the class

[Mai-Saad]

Working as expected
Note:

• failed tests need to be checked at the 1st alpha
• translations for dynamic list update while valid /invalid license shall be checked in the prerelease
  testrail-report-508.pdf