Only send JavaScript error DWC reports when actionable

Currently, many of these reports have no actionable information
associated with them. This CL updates the reporting logic to only upload
reports which are actionable. Additionally, the
`IOS.JavaScript.ErrorHasFilename` metric has been removed as we now
have enough information to understand that checking filename is not
sufficient to differentiate between a JS error from an injected feature
script and one from the webpage's script.

OBSOLETE_HISTOGRAMS=This histogram did not report useful information as errors with no filename could be from either the webpage or from Chrome's injected scripts.

Bug: 394203899
Change-Id: Ied77d165ce2ea240df8f925ef515c285ec481743
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/6209368
Auto-Submit: Mike Dougherty <michaeldo@chromium.org>
Reviewed-by: Rohit Rao <rohitrao@chromium.org>
Commit-Queue: Mike Dougherty <michaeldo@chromium.org>
Cr-Commit-Position: refs/heads/main@{#1415381}
NOKEYCHECK=True
GitOrigin-RevId: fded32467fb360e4b7cf20c0c657efcc386df908
1 file changed
tree: fb3723c89b80d73f7100901ac85b6b376dfcb946
  1. build/
  2. chrome/
  3. components/
  4. google_internal/
  5. intents/
  6. net/
  7. public/
  8. testing/
  9. third_party/
  10. tools/
  11. web/
  12. web_view/
  13. .swift-format
  14. BUILD.gn
  15. COMMON_METADATA
  16. DEPS
  17. DIR_METADATA
  18. features.gni
  19. OWNERS
  20. PRESUBMIT.py
  21. PRESUBMIT_test.py
  22. README.md
README.md

This directory holds code related to Chrome for iOS. See this document for a description of the structure underneath this directory.