Rectify `transformRequestsFunction` precedence rules

[janbuchar]

• See discussion in docs: fix enqueueLinks documentation on option interactions #3057
• @barjin can you please explain the desired state?

[barjin]

The enqueueLinks function now has multiple ways of setting label (and other properties) of the new requests.

        await enqueueLinks({
            regexps: [{ regexp: /https:\/\/crawlee\.dev\/.*/, label: 'regexps-label' }],
            label: 'global-label',
            transformRequestFunction: (request) => {
                if (request.url.includes('api')) {
                    request.label = 'transformed-label';
                }
                return request;
            },
        });

In the example above, the final request should imo get transformed-label as it's label. The precedence should be (lowest to highest):

1. label and other "global" options directly in the EnqueueLinksOptions. Overridden by:
2. Properties specified by regexps, globs, and other "pattern-focused" options. Overridden by:
3. transformRequestFunction