bug: Browser-based crawlers double increment session.usageCount

[barjin]

As mentioned in comments of #1836 , instances of BrowserCrawler track the session.usageCount incorrectly. This is caused (partially?) by a double increment of session.usageCount - first in BrowserCrawler:

crawlee/packages/browser-crawler/src/internals/browser-crawler.ts

Line 596 in f3927e6

if (session) session.markGood();

and then in BasicCrawler:

crawlee/packages/basic-crawler/src/internals/basic-crawler.ts

Line 1337 in d1a094a

crawlingContext.session?.markGood();

Reproduction

    const crawler = new PlaywrightCrawler({
        requestHandler: ({ session }) => {
            console.log(session?.getState().usageCount);
        },
        sessionPoolOptions: {
            maxPoolSize: 1,
        },
        maxConcurrency: 1,
    });

    await crawler.run([
        'https://example.org/1',
        'https://example.org/2',
        'https://example.org/3',
        'https://example.org/4',
        'https://example.org/5',
        'https://example.org/6',
        'https://example.org/7',
        'https://example.org/8',
        'https://example.org/9',
        'https://example.org/10',
    ]);

prints out only even numbers:

INFO  PlaywrightCrawler: Starting the crawler.
0
2
4
6
8
10
12
14
16
18

[barjin]

This likely happened as a result of fixes in #1709 - before, BasicCrawler and BrowserCrawler were touching different Session instances, so each incremented one and the code above would have returned the correct 0..9 sequence.

Since both methods are accessing the same Session instance now, we just have to remove the markGood call from BrowserCrawler?