fix: delete invalid envs

[dawsbot]

It seems that the only valid env in the filesystem is .env.bitmama. For ease of onboarding for folks (like myself), the invalid envs should be fixed or removed entirely. Here is the error I was getting:

yarn jest validations/clock.test.ts

...
getaddrinfo ENOTFOUND fiat-connect.sandbox.alphafortress.com
...

[silasbw]

@satish-ravi can you provide feedback?

[dawsbot]

It looks like a ton of prior partners or folks who had implemented an API have either changed or shut down the URLs which are placed in those envs that I removed @silasbw. My hunch would be that fixing them is preferred to removing them, but I don't have those relationships to check-in with those partners.

[satish-ravi]

I think we can remove everything except love-crypto and bitmama. I don't believe any of them have an active integration. We can look into fixing the love crypto url, but usually its just the testnet env that's used here for validation when the partner was first integrating, so likely its just not active.

[dawsbot]

I'm not sure what you mean @satish-ravi - so perhaps you could edit this PR and merge away. As a new developer I find it high-risk that there's only one env that works. If zero of the provided envs were to work I would have never began contributing and assumed this was a dead project 🙏

[silasbw]

It seems low risk and simple enough to re-add a config w/ some fixes.