[Docs] Streamline default poktrolld configurations

[Olshansk]

Objective

Make usage of poktrolld simpler by setting default configs (home directory, RPC node, etc...).

Origin Document

This was created as a result of multiple conversations from #947.

To limit the scope of #947 to the supplier cheatsheet, this ticket was created.

Goals

• Streamline the usage of poktrolld
• Ensure documents are consistent across the board (walkthroughs, cheatsheest, etc...)

Deliverables

• Update the documentation to leverage poktrolld config set client node
• Update the documentation to leverage poktrolld config home
• Ensure the old (POCKET_NODE env variable) & new approaches (configs above) are complimentary and clearly explained to the user
• Make the walkthroughs explain both but have the cheat sheets just leverage one
• Make sure that all walkthroughs and all cheat sheets are consistent
• Cross reference documentation with poktroll-docker-compose-example
• Remove the presence of $NODE_FLAGS when/where appropriate

Non-goals / Non-deliverables

• Force everyone to use poktrolld config for all operations
• Document poktrolld in detail
• [OPTIONAL] Create a new page called poktrolld config

---

Creator: @Olshansk
Co-Owners: @bryanchriswhite

[okdas]

This is good! Thanks.

New (I assume 0.52) cosmos-sdk will have clientconfig.DefaultClientConfigTemplate which will allow us to create a custom client config. I started working on this in #940 only to realize that functionality is not available on cosmos-sdk version we're using.

[Olshansk]

Noted @okdas. Moving this to the next iteration.