Add support for extension compatibility

[aledeg]

The compatibility does support only a minimum version of FreshRSS. If we need
something a bit more clever in the future, it is possible to handle a rule
with a bit more complexity.

See #5903

Changes proposed in this pull request:

How to test the feature manually:

Pull request checklist:

• clear commit messages
• code manually tested
• unit tests written (optional if too hard)
• documentation updated

Additional information can be found in the documentation.

[aledeg]

@Alkarex This is a first draft for the support of extension compatibility. Is there something else to add for a first version or we'll start with that?

I'll work on the extension list generation after this is completed.

[Inverle]

There has to be a white-space: nowrap CSS rule on the <th> element:

[aledeg]

There has to be a white-space: nowrap CSS rule on the <th> element:

What would be the css selector to apply that rule. I don't think I can apply it on th directly, the impact would be to important.
Do you have any idea?

[Inverle]

div.table-wrapper th?

[Frenzie]

You could always just add a class to that column (though I don't necessarily know if I agree with the comment :p)

[Alkarex]

/fix-all

[github-actions]

🤖 Command /fix-all received. Running…

[github-actions]

⚠️ Command /fix-all ran successfully, but changes could not be pushed.

• Please check that your PR settings “Allow edits from maintainers” is enabled.
• Or run make fix-all locally and push to your branch.

[Alkarex]

/fix-all

[github-actions]

🤖 Command /fix-all received. Running…

[github-actions]

⚠️ Command /fix-all ran successfully, but changes could not be pushed.

• Please check that your PR settings “Allow edits from maintainers” is enabled.
• Or run make fix-all locally and push to your branch.

[Alkarex]

/fix-all

[github-actions]

🤖 Command /fix-all received. Running…

[github-actions]

🔧 Command /fix-all made some fixes and committed as fa0d18e

[Alkarex]

Sorry @aledeg for using your PR as a test for implementing a new GitHub Action:

• GitHub Action: make fix-all (v5) #8098

I had to try a few times to get it to work...

[aledeg]

@Alkarex I think there is a rounding error when computing the completeness of translation. Maybe not an error but an incertainty.

[Alkarex]

@Alkarex I think there is a rounding error when computing the completeness of translation. Maybe not an error but an incertainty.

When new strings are added as is the case in this PR, then it is expected that the percentage will change

[aledeg]

@Alkarex I think there is a rounding error when computing the completeness of translation. Maybe not an error but an incertainty.

When new strings are added as is the case in this PR, then it is expected that the percentage will change

I mean that I ran the command make readme multiple times on my machine to fix that but there was not change detected. But on the CI/CD, changes were detected.

[Alkarex]

Try make fix-all (I have not tried the other ones in a long time, except make test-all)

[Alkarex]

I mean that I ran the command make readme multiple times on my machine to fix that but there was not change detected. But on the CI/CD, changes were detected.

Ah, but I cannot remember what the status was, but this might also be due to the fact that when updating the branch, it may import new strings that have recently been merged

[aledeg]

I've messed up. I've needed to make a rebase.