Windows: file path limit exceeded

[chrmod]

On some security configurations of Windows the file path is limited to 256 character. In this scenarios, Ghostery extension may fail to load if it is installed in a profile that's path is already relatively long.

Here is a list of longest file paths:

127 ./node_modules/@whotracksme/webextension-packages/packages/reporting/src/request/steps/token-telemetry/cached-entry-pipeline.js
120 ./node_modules/@whotracksme/webextension-packages/packages/reporting/src/request/steps/token-telemetry/token-pipeline.js
118 ./node_modules/@whotracksme/webextension-packages/packages/reporting/src/request/steps/token-telemetry/key-pipeline.js
116 ./node_modules/@whotracksme/webextension-packages/packages/reporting/src/request/steps/token-checker/token-domain.js
116 ./node_modules/@whotracksme/webextension-packages/packages/anonymous-communication/src/server-public-key-accessor.js
114 ./node_modules/@whotracksme/webextension-packages/packages/reporting/src/webrequest-pipeline/webrequest-context.js

It looks like the Anti-Tracking codebase is the culprit.

This issue is related to Ghostery 10 rollup and contributes to the list of problems listed in #1669

[chrmod]

We would probably do best to include a test if any of the files produced by build, does not exceed some desired length. Not sure what the limit should be, we can start with something not too constraining like a 100.