Add Address to list of basic types

[anton-trunov]

The page should explain the concept of addresses in TON and also combine all the functions that either consume or produce addresses.

This page should mention parseStdAddress and newAddress are inverse functions for each other.

Somewhere here:

[anton-trunov]

Storage requirements should be explained for addresses to avoid issues like #940. We should mention it in that page.

[novusnota]

Potentially depends on #1223

[anton-trunov]

Potentially depends on #1223

Let's resolve the issue as if that PR does not exist

[novusnota]

Potentially depends on #1223

Let's resolve the issue as if that PR does not exist

Ok, I'll try to leave the place for it and the potential future fix of #1119

[novusnota]

Note to self: add info about bounceable and non-bounceable "user-friendly" address representations. Especially that it's highly recommended to use, give and share non-bounceable addresses for wallet contracts (and why) and bounceable addresses for any other contract (and why).

https://docs.ton.org/v3/documentation/smart-contracts/addresses#bounceable-vs-non-bounceable-addresses

[novusnota]

Note to self: make sure all the references of chain / workchain ID (including basechain and masterchain) as well as hash / account ID lead to this new page and are well-explained on it. Currently, all such links lead to TON Docs.

[novusnota]

This!: https://docs.ton.org/v3/guidelines/dapps/cookbook#what-flags-are-there-in-user-friendly-addresses