fix: fix incompatible type of priv_validator_raddrs

[170210]

Description

This PR fix incompatible type of priv_validator_raddrs in TOML
The PrivValidatorRemoteAddresses was defined as string array, while the priv_validator_raddrs was of a string type rather than a slice type, which creates a mismatch with the structure of the configuration after parsing the toml file.
Related #692 & #707

[codecov]

Codecov Report

All modified and coverable lines are covered by tests ✅

Project coverage is 66.54%. Comparing base (fc54d22) to head (4ca0270).
Report is 3 commits behind head on main.

❗ Current head 4ca0270 differs from pull request most recent head 01814c0. Consider uploading reports for the commit 01814c0 to get more accurate results

Additional details and impacted files

@@            Coverage Diff             @@
##             main     #767      +/-   ##
==========================================
- Coverage   66.58%   66.54%   -0.04%     
==========================================
  Files         285      285              
  Lines       37919    37914       -5     
==========================================
- Hits        25248    25231      -17     
- Misses      10871    10881      +10     
- Partials     1800     1802       +2     

Files	Coverage Δ
config/config.go	79.36% <ø> (ø)
config/toml.go	74.19% <ø> (ø)
privval/internal/ip_filter.go	68.00% <ø> (-2.38%)	⬇️
privval/internal/null_object_filter.go	100.00% <ø> (ø)

... and 11 files with indirect coverage changes

[ulbqb]

Is it ok not to change parsing process although you change toml format?

ostracon/privval/internal/ip_filter_test.go

Lines 132 to 135 in ae67c39

	func TestIpFilterStringShouldReturnsIP(t *testing.T) {
	expected := []string{"127.0.0.1", "192.168.1.10"}
	assert.Equal(t, strings.Join(expected, ","), NewIpFilter(expected, nil).String())
	}

ostracon/privval/internal/ip_filter.go

Lines 29 to 31 in ae67c39

	func (f *IpFilter) String() string {
	return strings.Join(f.allowList, ",")
	}

And old processes are left.

[170210]

Is it ok not to change parsing process although you change toml format?

ostracon/privval/internal/ip_filter.go

Lines 29 to 31 in ae67c39

	func (f *IpFilter) String() string {
	return strings.Join(f.allowList, ",")
	}

I checked currently main branch and #707, this function hasn't been used yet (only used in test), so I think we just need to delete it.

[ulbqb]

Is it ok not to change parsing process although you change toml format?

[170210]

Is it ok not to change parsing process although you change toml format?

@ulbqb I think it is ok because after parsing with viper, it is read in as an array.

ostracon/config/config.go

Line 253 in ae67c39

PrivValidatorRemoteAddresses []string `mapstructure:"priv_validator_raddrs"`

[ulbqb]

I checked currently main branch and #707, this function hasn't been used yet (only used in test), so I think we just need to delete it.

Sorry, this is for Stringer interface so needed.