perf: Use Apify-provided environment variables to obtain PPE pricing information

[janbuchar]

• closes Load Actor pricing and charged events from env vars #481

[B4nan]

Let's call this perf optimization, that's the main point of why we do it, right?

[janbuchar]

E2E test is failing - I probably broke the charge limit logic

[metalwarrior665]

LGTM

[janbuchar]

https://github.com/apify/apify-sdk-js/actions/runs/18348147670 e2e test run - should be OK now

[barjin]

lgtm, thank you! 👍

I have a few ideas about the code quality, but neither is strictly necessary

[barjin]

nit: you have to call the new load* methods in this specific order, as loadChargedEventCounts reads variables initialized by loadPricingInfo (temporal coupling)

[barjin]

how about removing the load* method calls from the constructor, running them only once in the init method (at one call site) and conditionally loading the config with something like

async function getPricingInfo() {
   if (
        configuration.get('actorPricingInfo') &&
        configuration.get('chargedEventCounts')
    ) return { pricingInfo: JSON.parse(), ...

    const run = await this.apifyClient.run(this.actorRunId).get();
    ...
}

This would allow us to load the pricing info + events at one point in init like

...
const { pricingInfo ... } = await getPricingInfo();
this.loadPricingInfo( pricingInfo );
...

which is IMO cleaner than the current approach, which is conditional based on the current object state