* docs: record how the repo migration broke the release pipeline

Moving the repository between accounts left the release tool naming an
owner that only redirected. GitHub keeps those redirects alive, and
cli_pkg does not follow them on POST, so pkg-github-release failed with
307 Moved Permanently after every test job had already passed and the
v4.1.3 deploy published nothing.

The repository is back on leoafarias, so the owner constant itself is
correct and unchanged here. This only records why it is load-bearing, so
the next account move updates it deliberately instead of rediscovering
this through a failed release.

* chore: prepare v4.1.4 release

The 4.1.3 tag never published anything: the deploy failed at the GitHub
release step because the repository had moved accounts, so pub.dev,
Homebrew, Chocolatey, Docker and the binaries were all skipped. Releasing
the same changes as 4.1.4 rather than reusing the unpublished 4.1.3 tag.