Move from Beckn's hosted protocol server to self hosted

[karntrehan]

Description

Currently the postman collection shared with the concerned teams is using the protocol server instance hosted by the beckn team. We have created a fork of the same in our org here. However the fork on testing locally, shows that the track and update methods have not been configured, which is a bug that needs to be fixed. Post the bug fix, the protocol-server needs to be onboarded in samagra devops pipelines and deployed on our servers. Ideally, if everything goes well, the samagra deployed link would be a drop in replacement for the current beckn's instance in our use cases.

[karntrehan]

@techsavvyash spoke to beckn team. A fix was shared. Will followup with them. cc @charanpreet-samagra

[karntrehan]

We will refer the DSEP core.yaml file and implement in our branch.

[techsavvyash]

I have figured out the fix, and this ticket can now be closed and #16 can be worked on
cc: @karntrehan @charanpreet-samagra

[karntrehan]

We have deployed to samagra servers using pm2. Docker compose files of the protocol server are broken. We are fixing it in #16

[karntrehan]

Devops pipeline not used. Dockerised deployment instead.

[karntrehan]

Domain mappings to be done and tested.