Epic: Backports for v1.13.0-rc2

[SpicyLemon]

Summary

We're going to need a v1.13.0-rc2.

Here are some PRs that should be backported to it. Some of these should be done as their own PR while others can be combined.

• Backport 1.13: Update docs. #1154
  <- Small tweaks to the name restrictions documentation. #1137
  <- Update release process documentation. #1141
  <- Fix broken cosmos-sdk doc url #1150
• Backport 1.13: Dependabot bumps. #1155
  <- Bump google.golang.org/grpc from 1.49.0 to 1.50.0 #1140
  <- Bump github.com/btcsuite/btcd from 0.22.1 to 0.22.2 #1144
  <- Bump golang.org/x/text from 0.3.7 to 0.3.8 #1146
  <- Bump github.com/spf13/cobra from 1.5.0 to 1.6.0 #1147
  <- Bump technote-space/get-diff-action from 6.1.0 to 6.1.1 #1163
  <- Bump google.golang.org/grpc from 1.50.0 to 1.50.1 #1164
  <- Bump golang.org/x/text from 0.3.8 to 0.4.0 #1165
  <- Bump github.com/cosmos/cosmos-proto from 1.0.0-alpha7 to 1.0.0-alpha8 #1156
• Backport 1.13: wasmd bump. #1162
  <- Bump wasmd to v0.29.0-pio-1 #1148
• Backport 1.13: Github actions and scripts. #1166
  <- Reduce the number of configurations used for the sims tests. #1138
  <- Define concurrency for github actions. #1139
  <- Create check that time.Now isn't used unexpectedly. #1133
  <- Update devnet docker build to be current #1098
• Backport 1.13: Restricted Marker Transfer IBC #1167
  <- 1136 restricted marker transfer over ibc #1158
• Backport 1.13: ICA allowed messages #1170
  <- Updated handler to have no host module enabled messages #1168
• Backport 1.13: SDK 0.46.3 #1182
  <- Bump Cosmos-SDK to v0.46.3-pio-1 (from v0.46.2-pio-1). #1173

The PRs listed above are the original PRs to main.

To backport them to release/v1.13.x:

1. git checkout main && git pull
2. Use git log --oneline to identify the commit hash of the PR(s) desired.
3. git checkout release/v1.13.x && git pull
4. git checkout -b <user>/bp-<something>
5. Use git cherry-pick <commit hash> to apply a PR to your branch.
6. If there are any conflicts, fix them and commit.
7. Repeat 5 and 6 for each PR in the group.
8. Create a new PR from your branch with release/v1.13.x as the target branch.
9. A merge commit would better help git track similarities between main and release/v1.13.x. A squash and merge just makes the merge back to main a little messier.

---

For Admin Use

• Not duplicate issue
• Appropriate labels applied
• Appropriate contributors tagged
• Contributor assigned/self-assigned