docs: render orm and collections in docs

[julienrbrt]

Description

Now that both ORM and Collections docs are ready, add a packages section that renders the documentation for ORM and Collections.
Moves depinject documentation under that package section and setup redirects to not break links.
Add redirects about the capability module now that it lives in IBC (https://github.com/cosmos/ibc-go/tree/fdd664698d79864f1e00e147f9879e58497b5ef1/modules/capability)

After this section, we have:

• under /packages a list of all our packages (orm, collections, log, math, ...) - anything cosmossdk.io/*
• under /tools a list of all our tooling - anything under cosmossdk.io/tools/*
• under /modules section, once everything is extracted, is as well a list of cosmossdk.io/x/*

Inspired from https://golang.org/x page.

---

Author Checklist

All items are required. Please add a note to the item if the item is not applicable and
please add links to any relevant follow up issues.

I have...

• included the correct type prefix in the PR title
• added ! to the type prefix if API or client breaking change
• targeted the correct branch (see PR Targeting)
• provided a link to the relevant issue or specification
• followed the guidelines for building modules
• included the necessary unit and integration tests
• added a changelog entry to CHANGELOG.md
• included comments for documenting Go code
• updated the relevant documentation or specification
• reviewed "Files changed" and left comments if necessary
• confirmed all CI checks have passed

Reviewers Checklist

All items are required. Please add a note if the item is not applicable and please add
your handle next to the items reviewed if you only reviewed selected items.

I have...

• confirmed the correct type prefix in the PR title
• confirmed ! in the type prefix if API or client breaking change
• confirmed all author checklist items have been addressed
• reviewed state machine logic
• reviewed API design and naming
• reviewed documentation is accurate
• reviewed tests and test coverage
• manually tested (if applicable)

[tac0turtle]

packages is a bit if a weird name. I dont think adding another section like this is worth it. Can we add collections and orm to building modules and depinject to building apps

[julienrbrt]

packages is a bit if a weird name. I dont think adding another section like this is worth it. Can we add collections and orm to building modules and depinject to building apps

I was thinking of using this section for rendering as well, math, log, and all other helpful package README. Don't you think it's worth it?

[julienrbrt]

Improved it a bit, wdyt @tac0turtle? If we are exhaustive, then it makes sense imho.
Not extremely fan of the term Automation but I couldn't come up with better. It does make it sound cool.

[tac0turtle]

Packages is a go term so i guess it makes sense. Its not the most appealing but maybe we come up with something in the future