You can't have it all, no matter what you do.
How can I configure the web server to give me access from outside and still have Bonjour give me direct links to the wikis?
As David's already mentioned, running a server may violate your agreement with Verizon. Check that before you go much further.
Assuming, for now, that's all clear (either because it isn't against the rules, or you upgrade to a business-class service that permits it, you could get to your web server from the outside, but Bonjour would not work (Bonjour is, inherently, a local service discovery protocol that will not reach out across the internet.
So, #1 - you may be able to get the wiki accessible, but you can't use Bonjour remotely.
If you don't care about the agreement with Verizon and want to do it anyway then the simplest option would be to run the web server on a different port (e.g. 8080 rather than 80). This
may get around Verizon's block but now Bonjour doesn't work for internal users either (Bonjour may locate the server, but it likely won't notice the service/port number its moved to therefore no one, whether internal or external, will be able to use Bonjour to find your Wikis
So #2 you might be able to get around the block to make your wiki public, but not if you want to use Bonjour.
The last option would be to implement a VPN (assuming that's not also blocked by Verizon). The VPN would allow remote users to connect to your internal network and get to your wiki, but it wouldn't be generally available (only users with VPN accounts would be able to see it) and there are all kinds of issues with Bonjour over VPN (it may or may not work, or may take a lot of tweaking to get to work at all).
So #3 - you may be able to get remote users to connect via VPN, but bonjour is still likely to be an issue.
You'll need to prioritize your needs to decide whether remote users accessing the site, VPN users accessing the site, or Bonjour is your priority.