fix!: change the instrumentation config to circumvent viper bug

[evan-forbes]

Description

There's an viper property or potential bug that stops us from overriding the default values for slices of strings. The "solution" atm is to use a string and parse it later like animals later. Unfortunately I think this is breaking since we're changing what a config is doing so tbh I'm not sure if we can ever include this in v1. If that's the case then we might want to consider not merging this to v0.34.x-celestia and only to main.

closes #1141

[rootulp]

Unfortunately I think this is breaking since we're changing what a config is doing so tbh I'm not sure if we can ever include this in v1. If that's the case then we might want to consider not merging this to v0.34.x-celestia and only to main.

I'm in favor of merging this and cutting a new minor release (e.g. v1.30.0-tm-v0.34.29). I realize that technically breaks SemVer but I think the pro outweights the con.

Pro: feature parity between the branches we maintain
Con: breaking SemVer for releases on this repo

We expect the # of consumers of celestia-core to be few (ideally just celestia-app). Since we're responsible for bumping this dep in celestia-app, we also know that this minor release of celestia-core includes a breaking change.

[evan-forbes]

🤭 whoops thanks for the comment fix @rootulp