feat(integration-templates): [nan-1192] add checkr syncs and actions

[khaliqgant]

Describe your changes

Add checkr syncs and actions:

• GET /background-check/service-list: returns a possible list of services that Checkr can perform for a background check. Takes into account if the connection has account hierarchy enabled or not and returns the node the background check is associated with if so
• GET /background-check/service-parameters: obtains the parameters needed to trigger a background check for a particular background check
• POST /background-check/trigger: trigger a background check for a candidate
• POST /candidates: create a candidate to be able to trigger background checks for

Adds a single sync:

• GET /background-checks: retrieves all background checks for all candidates

Issue ticket number and link

NAN-1192

Checklist before requesting a review (skip if just adding/editing APIs & templates)

• I added tests, otherwise the reason is:
• I added observability, otherwise the reason is:
• I added analytics, otherwise the reason is:

[linear]

NAN-1192 Checkr 1st implementation

[TBonnin]

don't know enough about the provider to judge the business logic but code looks ok. Don't we want to systematically validate actions input with zod?

[TBonnin]

I feel it would be more readable if broken up into smaller functions:

export default async function runAction(nango: NangoAction): Promise<CheckrServicesResponse> {
    const { config, connection_config } = await constructRequestWithConnectionConfig(nango, '/v1/packages');
    const accountHierarchyEnabled = connection_config['accountHierarchyEnabled'] || false;

    let services: CheckrService[] = fetch({nango, config, endpoint: '/v1/packages'});

    if (accountHierarchyEnabled) {
        const nodes = await fetch({nango, config, endpoint: '/v1/nodes?include=packages'});
        services = process(nodes, services);
    }

    return { services };
}

async function fetch({nango, config, endpoint} : {nango: NangoAction, config: ProxyConfiguration, endpoint: string}) {
    const res = [];
    for await (const checkrServices of nango.paginate({ ...config, endpoint })) {
        res.push(...checkrServices);
    }
    return res;
}

function process(nodes: any[], services: CheckrService[]): CheckrService[] {
    return nodes.flatMap(node => {
        if(node.packages.length === 0) {
           return [];
        } else {
             return node.packages.map((pkg: string) => ({
                ...services.find(service => service.slug === pkg),
                node: node.custom_id
            }))
        }
    });
}

Haven't tested so details might be wrong

[khaliqgant]

Thanks, kept as is h/e

[bodinsamuel]

Looks good minor comments

[bodinsamuel]

imo comments are easier to understand at the exact position, I need to do a lot of back and forth to understand why it's done this way

[bodinsamuel]

is there any reason a connection would not have an acces_token?

[khaliqgant]

More of a check to make TS happy

[bodinsamuel]

english: not sure about the term mappers but it's not my main language, I would call them formatters maybe

[khaliqgant]

Thanks, IMO mappers is clear