Update Markdown Table Editor to 11.1.0

[krotname]

Updates Markdown Table Editor from 11.0.2 to 11.1.0 for x86, x64 and arm64.

Release: https://github.com/krotname/NppMarkdownTableEditor/releases/tag/v11.1.0

This replaces the earlier 11.0.4 revision of this PR while it was still open, so the list moves straight to the current release.

What changed in the plugin

11.0.4 was a bug-fix release for the Markdown table engine:

• a separator line right after a table no longer starts a second, overlapping table that reused the
  previous table's last row as its header, which could corrupt a document when reformatting;
• tables written without outer pipes keep the outer pipe whenever the first or last column holds an
  empty cell, so inserting a column no longer silently drops one on the next parse;
• deleting down to a single column in such a table no longer leaves rows without any pipe at all;
• a header made only of dashes is no longer mistaken for the separator row.

11.1.0 adds no functional change on top of that. It aligns versions and licensing across the whole
Markdown Table Editor suite - this plugin, the JetBrains IDE plugin, and the shared
markdown-table-core library now all ship as GPL-3.0-or-later under one version number.

Checksums

Platform	SHA-256 of the pluginadmin ZIP
x86	8d5b66e539cceef2bce664433616eacdf57c22cbd590d155f11c5d6266877bf5
x64	a39a5f4cce2b726c585b80d142c755b1d2cd7cd3ef8c1afe6e3be41c0ff5fa40
arm64	37ed2e3ac28b514d3267e9bcd0cca18683d67ae817075e9f91a5b944c78e18ea

They match the SHA256SUMS.txt published with the release, and each ZIP carries a
MarkdownTableEditor.dll with file version 11.1.0.0.

[krotname]

Heads-up on the red build (Release, x64) check: it is a transient network failure on the runner, not a problem with this change.

The validator hit ConnectionResetError(10054, 'An existing connection was forcibly closed by the remote host') while downloading plugin archives, and it hit four unrelated entries in the same run — Another Markdown, NppEventExec, pycalc and this one. build (Release, Win32) and build (Release, arm64) validated the very same three JSON files and passed.

Locally python validator.py x86, x64 and arm64 all exit 0 against this branch, so the SHA-256 ids and the download URLs resolve correctly.

I do not have rights to re-run the job here — a re-run should turn it green.

[krotname]

For the record, I opened #1145 to fix the underlying cause of the red check here: the validator downloads every plugin archive with a single requests.get that has no retries and no timeout, so one dropped connection on any entry fails the whole job. That PR adds retries with backoff and a timeout, and its CI is green on all three platforms.

This PR itself still needs a re-run to clear the transient failure.