haozhan9

1. check all the keys and values of Shield module to identify the existence of "certik" address prefix 2. Change the "certik" prefix to "shentu" 3. modify the test code...

1. check all the keys and values of Shield module to identify the existence of "certik" address prefix 2. Change the "certik" prefix to "shentu" 3. modify the test code...

1. check all the keys and values of Shield module to identify the existence of "certik" address prefix 2. Change the "certik" prefix to "shentu" 3. modify the test code...

Excluding the modules - cert, oracle, shield, modify the test code to cover both the address prefix of "certik" and "shentu" cases.

For the events containing the bech32 address (`certik***`), make a change to the `EventManager` to emit a duplicate copy that contains the equivalent shentu-prefixed address.

1. check all the keys and values of Cert module to identify the existence of "certik" address prefix 2. Change the "certik" prefix to "shentu" 3. modify the test code...

1. check all the keys and values of Oracle module to identify the existence of "certik" address prefix 2. Change the "certik" prefix to "shentu" 3. modify the test code...

1. check all the keys and values of Shield module to identify the existence of "certik" address prefix 2. Change the "certik" prefix to "shentu" 3. modify the test code...

1. check all the keys and values of Staking module to identify the existence of "certik" address prefix 2. Change the "certik" prefix to "shentu" 3. If appliable, modify the...

please follow the idioms of cosmos modules and existing shentu modules.