[Awaiting Payment May 16th] [Wave Collect] [Xero] Put Xero display logic under a specific beta

[lakchote]

We need to put Xero under a specific beta since QBO will be released sooner and they share the same accounting menu.

[ShridharGoel]

Proposal

Please re-state the problem that we are trying to solve in this issue.

Put Xero in beta.

What is the root cause of that problem?

New change.

What changes do you think we should make in order to solve the problem?

Add the below logic in PolicyAccountingPage:

const {canUseXeroIntegration} = usePermissions();

const accountingIntegrations = Object.values(CONST.POLICY.CONNECTIONS.NAME).filter((name) => {
    if (name === CONST.POLICY.CONNECTIONS.NAME.XERO) {
        if (!canUseXeroIntegration) {
            if (!!policy?.connections?.xero || connectionSyncProgress?.connectionName === CONST.POLICY.CONNECTIONS.NAME.XERO) {
                return true
            }
            return false
        }
    }

    return true
});

This will ensure that Xero will not show only if it's not already connected.

In Permissions.ts:

function canUseXeroIntegration(betas: OnyxEntry<Beta[]>): boolean {
    return !!betas?.includes(CONST.BETAS.XERO_INTEGRATION) || canUseAllBetas(betas);
}

[lakchote]

@ShridharGoel since I've assigned myself already, no need to submit proposals. Thank you.

[trjExpensify]

Deployed to prod 9 hours ago. Assigning Rushat for the PR review.

[trjExpensify]

Payment summary as follows:

$250 to @rushatgabhane for the C+ review of the PR

[trjExpensify]

Payment will be handled centrally when we wrap the project, we can close this as the regression period is over.