feat: Export create_associated_token_account and create_associated_token_account_idempotent

[cryptopapi997]

Currently when working with tokens in anchor client, most of the basic operations can be done because anchor_spl exposes them e.g. we can create a token, mint it, transfer it, etc. The only thing in a "basic" token workflow that cannot be done is create associated token accounts.

I don't know why this is, but I'd imagine it's because at the time that anchor_spl was first written ATAs weren't the default yet and normal token accounts could be created with it on the client side. Nowadays this has changed though, so I believe updating the exports to expose ATA creation is appropriate.

[vercel]

@cryptopapi997 is attempting to deploy a commit to the coral-xyz Team on Vercel.

A member of the Team first needs to authorize it.

[acheroncrypto]

Currently when working with tokens in anchor client, most of the basic operations can be done because anchor_spl exposes them e.g. we can create a token, mint it, transfer it, etc. The only thing in a "basic" token workflow that cannot be done is create associated token accounts.

I don't know why this is, but I'd imagine it's because at the time that anchor_spl was first written ATAs weren't the default yet and normal token accounts could be created with it on the client side. Nowadays this has changed though, so I believe updating the exports to expose ATA creation is appropriate.

It's most likely because anchor-spl crate was intended for CPI:

anchor/spl/Cargo.toml

Line 7 in efe2e40

description = "CPI clients for SPL programs"

Most of those exports have been added later too.

[acheroncrypto]

Thanks!