v0.4.1 — publish the resolver fix

Publishes the resolver fix from #15.

The fix merged yesterday but the version stayed at 0.4.0, so npm i @moshcoder/moshpit-dns kept installing a bridge that answered ANSWER: 0 for names that resolve perfectly well.

That authoritative-empty answer is the worst failure shape available: the client treats it as final, dig reports the name exists, and nothing logs an error — so it reads as "Moshpit is broken" with no thread to pull.

Upgrade: npm i -g @moshcoder/moshpit-dns@0.4.1

A running bridge is not restarted by upgrading the package — moshpit-dns disable then enable to pick it up.