feat(CosmosFullNode): Allow more configuration of p2p services

[DavidNix]

Closes https://github.com/strangelove-ventures/cosmos-operator/issues/310

Here's an example of a p2p service that's been configured as a NodePort.

apiVersion: v1
kind: Service
metadata:
  annotations:
    app.kubernetes.io/ordinal: "0"
  creationTimestamp: "2023-08-02T16:01:43Z"
  labels:
   # ...
  name: cosmoshub-testnet-fullnode-p2p-0
  namespace: strangelove
  ownerReferences:
  - apiVersion: cosmos.strange.love/v1
    blockOwnerDeletion: true
    controller: true
    kind: CosmosFullNode
    name: cosmoshub-testnet-fullnode
    uid: a0f476d3-2fe8-4015-839a-fa5a45e78089
  resourceVersion: "16316491"
  uid: 835147f2-cf0b-48a8-bbcb-2096658028f4
spec:
  clusterIP: 10.8.165.63
  clusterIPs:
  - 10.8.165.63
  externalTrafficPolicy: Local
  internalTrafficPolicy: Cluster
  ipFamilies:
  - IPv4
  ipFamilyPolicy: SingleStack
  ports:
  - name: p2p
    nodePort: 30357
    port: 26656
    protocol: TCP
    targetPort: p2p
  selector:
    app.kubernetes.io/instance: cosmoshub-testnet-fullnode-0
  sessionAffinity: None
  type: NodePort
status:
  loadBalancer: {}