feat: add ws_protocol option

[amrbashir]

Checklist

• Updated CHANGELOG.md describing pertinent changes.
• Updated README.md with pertinent info (may not always apply).
• Updated site content with pertinent info (may not always apply).
• Squash down commits to one or two logical commits which clearly describe the work you've done. If you don't, then Dodd will 🤓.

Sometimes it is necessary to use ws: instead of wss:, this was encountered while working on a project for tauri (on android) where using wss: wasn't possible.

[thedodd]

Thanks for taking the time to open this PR! I think this is a valuable changeset. A few things which I think we should do:

• Let's update the website to document this new configuration option.
• We should use an enum in the Rust code to declare the two available values, either Ws or Wss.
• If the value is left unspecified, then this should default to the current behavior where we match the site's http/https protocol.
• In the autoreload.js, instead of checking for the interpolated {{protocol}} value of 'auto', we should just interpolate an empty string if left unspecified, and then trigger the http/https matching behavior.

Thoughts?

[amrbashir]

I added all required changes except this:

Let's update the website to document this new configuration option.

The website doesn't contain all configuration options and I am not sure where to include this one, isn't it enough to include it in the example configuration file?

[github-actions]

This PR is stale because it has been open 45 days with no activity. Remove stale label or comment or this will be closed in 10 days.

[amrbashir]

Is there anything left to do before this PR can get merged?

[ctron]

@amrbashir unfortunately I can't easily cherry-pick this into trunk-ng due to recent changes. If you want to rebase and raise a PR with trunk-ng, I could merge it.

[github-actions]

This PR is stale because it has been open 45 days with no activity. Remove stale label or comment or this will be closed in 10 days.

[ctron]

IIRC, this was already merged into trunk-ng.

[ctron]

This was brought back to trunk with PR #623 and it should be part of the next release of trunk too.

[amrbashir]

nice, I guess I can close this now