Fix for protonvpn update-port.sh

[BigRedBrent]

Disabled exiting on errors to allow the script to keep running even if commands fail, so that it can retry after 45 seconds on the next loop. (I've let the script run for several days, and it looks like this has resolved the issue of it stopping prematurely.)

Returned functionality to allow and deny ports in the firewall as necessary.

Modified the bind_trans function to be less complicated. Removed multiple attempts per loop, because it can retry after 45 seconds on the next loop.

Will now double check to make sure the port has actually changed on the next 45 second loop. This seems to catch incorrect port changes, or at the very least does not switch to a very short lived port change.

Breaking change

<placeholder>

Proposed change

<placeholder>

Type of change

• Bugfix (non-breaking change which fixes an issue)
• New provider (thank you!)
• Updated provider (thank you!)
• New feature (which adds functionality to a provider script/repo usage)
• Breaking change (fix/feature causing existing functionality to break)

Additional information

• This PR fixes or closes issue: fixes #
• This PR is related to issue: relates to #
• Link to documentation updated (if done separately): https://...

Checklist

• The code change is tested and works locally.
• There is no commented out code in this PR.

If user exposed functionality or configuration variables are added/changed:

• Documentation added/updated

[BigRedBrent]

I've been running this script for a while now, and it seems to work really well with the changes I've made.