REST client: always set Exclude value in accountInformationParams

[cce]

Summary

Small tweak, this sets the "exclude" parameter for both all/none cases used by the algod RestClient.AccountInformationV2 method, rather than an empty string for one of the cases.

Test Plan

Existing tests should pass.

[tsachiherman]

Wouldn't we want to keep the old endpoint also support the empty form for backward compatibility ?

[tsachiherman]

Is this related to any particular undesired behavior you've seen ?

[algonautshant]

Can you please also check (and fix) the comments below (lines 493-499):

// AccountAssetInformation gets account information about a given app.
func (client RestClient) AccountAssetInformation(accountAddress string, assetID uint64) (response generatedV2.AccountAssetResponse, err error) {
	err = client.get(&response, fmt.Sprintf("/v2/accounts/%s/assets/%d", accountAddress, assetID), nil)
	return
}
// RawAccountAssetInformation gets account information about a given app.
func (client RestClient) RawAccountAssetInformation(accountAddress string, assetID uint64) (response []byte, err error) {
	var blob Blob
	err = client.getRaw(&blob, fmt.Sprintf("/v2/accounts/%s/assets/%d", accountAddress, assetID), rawFormat{Format: "msgpack"})
	response = blob
	return
}

[cce]

a different fix would be to have the client not pass "?exclude" at all if the Exclude string is empty. This is conforming to the spec. To pass ?exclude=&somethingelse=Y as the client is doing is not conformant.