Improve 'abort-on-stack-trace' — add StackDepth support

[Yuki2718]

Compare these commits:
AdguardTeam/AdguardFilters@d466f3a
uBlockOrigin/uAssets@ee77cdf

As both the script and function names are randomized, StackDepth or the number of lines in the stack logs may be the only clue to distinguish legit and anti-adb calls. I guess it's actually possible to utilize StackDepth by complex regex, as AG logs stack trace in multiline mode (uBO logs in singleline mode), but I gave up as it's too complicated. For the above commit I happend to find the names are not totally random and exploited that the 4-th character is always numbers, but this was only fortune.

[Yuki2718]

Also, current stack logs on Chrome only includes the file name and not path as shown in #469. It's better if we can use full URL.