idl: Fix using address constraint with non-const expressions

[acheroncrypto]

Problem

IDL generation fails if you use non-const expressions with the address constraint:

#[derive(Accounts)]
pub struct MyIx {
    #[account(address = my_account.authority()])
    pub authority: Signer<'info>,
    pub my_account: Account<'info, MyAccount>,
}

#[account]
pub struct MyAccount {
    pub authority: Pubkey,
}

impl MyAccount {
    pub fn authority(&self) -> Pubkey {
        self.authority
    }
}

We had a similar problem in #2912, but that was only specific to field expressions and was fixed in #3034.

Summary of changes

Rather than assuming all expressions (other than field expressions) are valid for the address field (in the IDL), only assume the following expressions are valid:

• If the last segment of the path is all uppercase (const) e.g. my_program::ID
• Function call with no arguments (const fn) e.g. my_program::id()

For everything else, skip the address field resolution.

[vercel]

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

A member of the Team first needs to authorize it.