ux: add HTTP prefix to publish command output.

[elithrar]

Prefix "https://" in front of the "script available" output to allow shells to automatically detect it as a link.

This was the only relevant instance - e.g. other instances are typically referring to the domain structure, and not a deployed script.

/mnt/c/Users/Gamer/repos/wrangler (master) ✔ ➜  rg '\.workers\.dev'
README.md
63:    By default, `publish` will make your worker available at `<project-name>.<subdomain>.workers.dev`.
66:    explicitly enable deployment to `<project-name>.<subdomain>.workers.dev`, you can set `private = false`. 
npm/README.md
63:    By default, `publish` will make your worker available at `<project-name>.<subdomain>.workers.dev`.
66:    explicitly enable deployment to `<project-name>.<subdomain>.workers.dev`, you can set `private = false`. 
src/commands/subdomain.rs
65:        "{} Registering your subdomain, {}.workers.dev, this could take up to a minute.",
92:                "⛔ This account already has a registered subdomain. You can only register one subdomain per account. Your subdomain is {}.workers.dev \n Status Code: {}\n Msg: {}",
src/commands/publish/mod.rs
175:            "🥳 Successfully made your script available at {}.{}.workers.dev",

[elithrar]

Example:

🍺 Successfully published your script..
🍺 Successfully made your script available at https://lb-functions-example.silverlock.workers.dev
✨ Success! Your worker was successfully published. ✨

[ashleygwilliams]

thank you so much for the thoughtful PR! <3