Modify JupyterHub networkPolicy to match existing policy

[iameskild]

Reference Issues or PRs

What does this implement/fix?

Fixes #1965

Having the CHP networkPolicy enabled for JupyterHub deployed to AWS, Azure and GCP was no trouble so I'm not sure why this only seems to affect Digital Ocean. We also have the networkPolicy disabled for hub and singleuser already.

We should definitely test this change on the other clouds before merging - I don't expect this to cause problems since removing the network policy makes internal networking more permissible.

Put a x in the boxes that apply

• Bug fix (non-breaking change which fixes an issue)
• New feature (non-breaking change which adds a feature)
• Breaking change (fix or feature that would cause existing features not to work as expected)
• Documentation Update
• Code style update (formatting, renaming)
• Refactoring (no functional changes, no API changes)
• Build related changes
• Other (please describe):

Testing

• Did you test the pull request locally?
• Did you add new tests?

Any other comments?

[iameskild]

@costrouc do you see any reason why we shouldn't disabled the chp.networkPolicy?

[sblair-metrostar]

lgtm

[iameskild]

@pavithraes @kcpevey could you please review?

[pavithraes]

Thanks!