Use .config for frontend instead of env's

[technophile-04]

Description

Added a scaffold.config.ts in frontend instead for now as discussed in #231.

Updated network.ts now it uses block explores links from targetNetowork and now you get transaction link for different blockexplores previously it used only show for etherscan and dai.... its the same as #231 (comment)

would love to make it more robust and inline in different PR 🙌

Flow :

1. targetNetwork from scaffold.config.ts is single source of truth now for frontend
2. Removed .env.* and added them inside scaffold.config.ts

[carletex]

Hey @technophile-04 great job!

Left a few comments.

I think this should be the way to go, right? At least initially. (instead of #231 )

[technophile-04]

I think this should be the way to go, right? At least initially. (instead of #231 )

Yes for now 🙌, also added a small comment #231 (comment) there for the need of this PR

[sverps]

One thing I'm not sure about: inlining scaffoldConfig.targetNetwork or scaffoldConfig.targetNetwork.id or scaffoldConfig.targetNetwork.name directly. In some cases I think I'd have done something like

It doesn't really bother me. It's a little more verbose, but at the same time it makes it obvious where the value is coming from (scaffold config), rather than abstracting this knowledge away.

Maybe we can improve it a bit by making the scaffold config a named export, and naming the const simply scaffold. That reduces verbosity, makes sure it's named the same all over for recognisability, and reads nice: scaffold.targetNetwork.id

[carletex]

Great job everyone!

Merged this. Let's see how it feels, and don't forget about #231