bug: incorrect BasicCrawler clean up after CriticalError

[barjin]

As reported by @danielcrabtree under #2777 , Crawlee expects CriticalError to bring the entire process down and doesn't clean up all parts of the crawler correctly.

Example:

import log from '@apify/log';
import { CheerioCrawler, CriticalError } from 'crawlee';

log.setLevel(log.LEVELS.DEBUG); // to see the culprit

const crawler = new CheerioCrawler({
    requestHandler: async () => {
        throw new CriticalError('Critical error! The crawler won\'t recover from this!');
    },
    statusMessageLoggingInterval: 1, // to see the culprit faster
});

try {
    await crawler.run(['https://crawlee.dev']);
} catch (e) {
    // We catch the critical error here, so the process doesn't crash.
    // Right after this catch clause, the process should exit with code 0, 
    // But it will hang indefinitely instead because of the periodic logging `setInterval` hogging the event loop.
}

Proposed solution:

Revise the BasicCrawler.run method and ensure all timeouts / intervals / ... are cleared correctly in all the possible execution branches.