docs: Add VPN section to FAQ

[Oakleafknight06]

Added a vpn section to the FAQ, noting specifics about proton and mullvad. First sentence likely needs more details.

[Oakleafknight06]

It says I need commit signature verification. Should I set that up as per https://docs.github.com/en/authentication/managing-commit-signature-verification/about-commit-signature-verification#ssh-commit-signature-verification

[RoyalOughtness]

It says I need commit signature verification. Should I set that up as per https://docs.github.com/en/authentication/managing-commit-signature-verification/about-commit-signature-verification#ssh-commit-signature-verification

yes please

[RoyalOughtness]

see above

[Oakleafknight06]

It says I need commit signature verification. Should I set that up as per https://docs.github.com/en/authentication/managing-commit-signature-verification/about-commit-signature-verification#ssh-commit-signature-verification

yes please

Set this up. How does this affect the unsigned commit already committed? Do I need to do anything to fix that?

[RoyalOughtness]

It says I need commit signature verification. Should I set that up as per https://docs.github.com/en/authentication/managing-commit-signature-verification/about-commit-signature-verification#ssh-commit-signature-verification

yes please

Set this up. How does this affect the unsigned commit already committed? Do I need to do anything to fix that?

you can either squash into a new signed commit, or i can temporarily bypass for this pr :)

[Oakleafknight06]

It says I need commit signature verification. Should I set that up as per https://docs.github.com/en/authentication/managing-commit-signature-verification/about-commit-signature-verification#ssh-commit-signature-verification

yes please

Set this up. How does this affect the unsigned commit already committed? Do I need to do anything to fix that?

you can either squash into a new signed commit, or i can temporarily bypass for this pr :)

Attempted to squash, but it didn't seem to work.
(This is what I ran:)

> git commit -a -S -m "typo fix"
> git rebase -i HEAD~2
> git rebase --continue
> git push

Admittedly I am not very familiar with git, the most I have used it is for my bluebuild custom image. Can you either tell me how I should be doing this, or make the exception for the first commit like you said?

[Oakleafknight06]

If I have made the requested change, should I click the "resolve conversation" button where you requested said changes?

[Oakleafknight06]

I believe this should be good to go, however, I have issues with trying to run and test Jekyll locally (and don't have the time to fix that right now) so I have not tested that the images show up on the website correctly (as I am not sure how the image rendering / sizing works without that.)

[EsseLowNitro]

This is a problem I let slide and likely should be fixed categorically with CSS.

[Oakleafknight06]

Makes sense. Should the CSS fix be in this pull request, or somewhere separate?
Also, how did you access the preview site? I’m unaware of how that works

[EsseLowNitro]

I made a separate pull request for this image fix (#99).

Cloudflare deploys previews (branch-name.secureblue.pages.dev) for repo branches other than live, which goes into production (secureblue.dev), and creating branches directly on the repo is something @RoyalOughtness and I have access to. I made a temporary branch copying the changes of your PR to test it.

This can be improved in the future if a good local testing workflow is figured out, which could then be documented in this project's readme. But at least, with #99 getting merged, all images are guaranteed to render properly from then on.