Adding waitForTimeout/waitForSelector for assets discovery browser when JS is enabled

[amandeepsingh333]

• added waitForTimeout and waitForSelector at the time of discovery when JS is enabled

so now waitForTimeout and waitForSelector are at 2 places:

• snapshot level (snapshot.waitForTimeout)
• discovery level (snapshot.discovery.waitForTimeout)

usage of both:

when it is passed at snapshot level => these options are used before a DOM snapshot is taken. The primary goal is to ensure that the page has fully loaded and any necessary DOM elements are present before capturing the state of the page. This mode is currently only supported when used with percy snapshot cli command.

when it is passed at discovery level and JS is enabled => in this phase, these options are used to wait for specific assets or network requests to be discovered and captured. The asset-discovery process often occurs during or after initial page load, and some resources may not be immediately available.

how client should use:

snapshot level => You should use these options at the snapshot level when you want to ensure the readiness of a page before it is captured. This ensures that no partial or incomplete content is included in the snapshot.

discovery level => You should use these options in the discovery level when you are facing issues with missing assets or incomplete network requests. By waiting for the selector or a set timeout, you give enough time for assets to load

• used both at the time of discovery
• added test cases for the same

[this-is-shivamsingh]

1. Please Update the PR description and PR title as well

[this-is-shivamsingh]

• Test with any sdk, if it working [ means if you are getting the value passed from the sdk -> CLI ]
• Add 1 more test where we also send domSnapshot with percy.snapshot because this cover the SDK flow as well, as in sdk flow we send domSnapshot