Auto capture and insert cookie in asset discovery browser

[chinmay-browserstack]

• Capture cookies using document.cookie in serialize-dom so can be used in asset discovery.
• Use this cookie and insert in asset discovery browser.
• Disable this behaviour using PERCY_DO_NOT_USE_CAPTURED_COOKIES env variable
• Prioritise cookie passed via percy.yml over auto captured cookie.

Note: httponly cookie can't be captured so that needs to be passed using percy.yml

[rishigupta1599]

LGTM

[davidrunger]

@chinmay-browserstack @prklm10 I think that this PR is causing me to see the following warning in my logs:

[percy] Invalid snapshot options:

There is no additional logging about what the specific invalid snapshot options are; only that log line is printed.

Example here: https://github.com/davidrunger/david_runger/actions/runs/10013824950/job/27682261695#step:10:231

Part of the reason that I believe that this PR is the cause of that warning being logged is because if I open this file on my local machine -- node_modules/.pnpm/node_modules/@percy/config/dist/validate.js -- and if I add the following to the top of the validate function that is defined therein on L186, then I stop seeing the log line about [percy] Invalid snapshot options: when I run my test:

delete data.domSnapshot.cookies;

I tried this because when (before making the just-mentioned addition) I logged ajv.errors, part of the output included this:

    // ...
    keyword: 'unevaluatedProperties',
    params: { unevaluatedProperty: 'cookies' },
    message: 'must NOT have unevaluated properties',
    // ...

[davidrunger]

Also, downgrading from @percy/cli 1.29.0 to 1.28.9 fixes the issue (i.e. causes [percy] Invalid snapshot options: not to be logged anymore).

[chinmay-browserstack]

@davidrunger Thanks for pointing this out. i have checked and found cookies field is missing from config as you mentioned.

Created a fix PR for it #1669. it will be fixed in next release.
Meanwhile you can continue using @percy/cli 1.29.0 as it just prints warning and has no impact on any functionality of percy cli.