Rename Portal to Gateway (#47)

- Reverting this commit: #29

![Screenshot 2023-10-03 at 10 05 20 AM](https://github.com/pokt-network/pocket-network-protocol/assets/1892194/f28ee993-f33d-4e08-b3c0-2ad97c57182d)

utility/.ideas.md

@@ -5,7 +5,7 @@ There are lots of ideas that have been discussed
 ## Session Protocol
 
 - [ ] Look into more fluid mechanisms of moving rate limits across a cluster of Servicer's rather than simply `Relays / NumServicers`
-  - [ ] Explain that Portal could help in redirecting traffic in the right direction
+  - [ ] Explain that Gateway could help in redirecting traffic in the right direction
 - [ ] Define the protocol for "Session Fuzzing" to account for relays sent/serviced close to session boundaries
 - [ ] Enable multiple RelayChains per session
 
@@ -15,10 +15,10 @@ There are lots of ideas that have been discussed
 - [ ] Enable revenue sharing through multiplicity of the OperatorPublicKey
 - [ ] Expand Rate Limiting algorithm so different requests cost different amounts
 
-## Portal Protocol
+## Gateway Protocol
 
-- [ ] If an Application delegates to multiple portals, add a mechanism that monitors how many relays each portal can do; https://github.com/pokt-network/pocket-network-protocol/pull/25/files#r1091248703
-- [ ] Rename Portal Actor to Portal Actor
+- [ ] If an Application delegates to multiple gateways, add a mechanism that monitors how many relays each gateway can do; https://github.com/pokt-network/pocket-network-protocol/pull/25/files#r1091248703
+- [ ] Rename Gateway Actor to Gateway Actor
 - [ ] Iterate and expand on incentive / penalization mechanisms (lots of opportunity here)
 - [ ] Provide details for off-chain "business models" enabled by Pocket
 
@@ -37,7 +37,7 @@ There are lots of ideas that have been discussed
 
 ## General
 
-- [ ] All staked actors (DAO, Portals, Fisherman, etc...) get a fraction of the block rewards for continued incentives
+- [ ] All staked actors (DAO, Gateways, Fisherman, etc...) get a fraction of the block rewards for continued incentives
 - [ ] Integration with protocols like NYM or HOPR for native opt-in RPC security / mixing / obfuscation
 - [ ] Multiple operator / output addresses per actor
 - [ ] Delegated staking (validation, servicing, monitoring, etc...)
@@ -84,7 +84,7 @@ sequenceDiagram
     title Address Swap Attack
 
     actor C as Client
-    participant P as Portal<br><br>(Pocket Network Inc.)
+    participant P as Gateway<br><br>(Pocket Network Inc.)
     participant SN as Servicer<br><br>(Permissionless Actor)
     participant BN as Blockchain<br><br>(Owned by Servicer)