Fix missing registry URL, schema location, and testnet IDs in local-simple-bap.yaml

[mohammadparvez921]

While running the onix container using the local-simple-bap.yaml template, the node failed during the validateSign and validateSchema steps. Debugging the initialization logs revealed that the default configuration is missing critical endpoints for the registry and schema validator, and lacks the necessary network IDs to communicate with the India Energy Stack test network.

Modifications Required:
The following parameters are missing or incomplete in both the bapTxnReceiver and bapTxnCaller modules:

1. Registry Plugin (registry)
   Missing the registry URL and the correct testnet IDs.
   Current (Incorrect):

registry:
  id: dediregistry
  config:
    registryName: subscribers.beckn.one
    allowedNetworkIDs: "nfh.global/testnet-deg,indiaenergystack.in/winroom-ies-data-exchange"

Fix (Correct):

registry:
  id: dediregistry
  config:
    url: https://fabric.nfh.global/registry/dedi
    registryName: subscribers.beckn.one
    allowedNetworkIDs: "nfh.global/testnet-deg,indiaenergystack.in/winroom-ies-data-exchange,indiaenergystack.in/test-ies-data-sharing-network"

2. Schema Validator (schemaValidator)
   Missing the type and location parameters, causing the validator to fail initialization.
   Current (Incorrect):

schemaValidator:
  id: schemav2validator
  config:
    cacheTTL: "3600"
    # ...

Fix (Correct):

schemaValidator:
  id: schemav2validator
  config:
    type: url
    location: https://raw.githubusercontent.com/beckn/protocol-specifications-v2/main/api/v2.0.0/beckn.yaml
    cacheTTL: "3600"
    # ...

(Note: The keyManager block also needs standard updates for local keys and network participant IDs to fully run, which I have done locally).

Impact:
Without these parameters, the BAP node drops incoming payloads and fails to handshake with the network. Applying these fixes resolves the runtime errors in the onix container and allows successful schema and signature validation.