should we ban getTimezoneOffset

[patmmccann]

Is this useful to adapters? Especially since we allow

Prebid.js/libraries/smartyadsUtils/getAdUrlByRegion.js

Line 14 in 5df0005

const timezone = Intl.DateTimeFormat().resolvedOptions().timeZone;

?

[dgirardi]

That's one of the few called out as still missing a codeql rule from #13935, and actually weighed worse than getTimeZoneOffset:

"Date.prototype.getTimezoneOffset": 16.79,
"Intl.DateTimeFormat.prototype.resolvedOptions": 20.01,

[dgirardi]

I believe it's possible to calculate the offset without asking for it directly, asking for formatted dates in UTC and local time.

[patmmccann]

"Intl.DateTimeFormat.prototype.resolvedOptions": 20.01, is more useful than getTimezoneOffset; it appears widely used for datacenter routing. offset feels redundant or not particularly useful