fix some broken crbug.com links in markdown docs

Otherwise gitiles renders these as (broken) relative links.

Change-Id: I66fffdf2e9934bfa7ced35f2850d528a2bbfa947
Reviewed-on: https://chromium-review.googlesource.com/1148046Reviewed-by: Dirk Pranke <dpranke@chromium.org>
Reviewed-by: Peter Beverloo <peter@chromium.org>
Commit-Queue: Mostyn Bramley-Moore <mostynb@vewd.com>
Cr-Commit-Position: refs/heads/master@{#577616}

chrome/android/java/src/org/chromium/chrome/browser/notifications/channels/README.md

@@ -71,7 +71,7 @@ for newly created channels, where appropriate. See [the setDescription documenta
 
 > **Important**: As of October 2017, instrumented channel tests are not run on trybots because
  these tests are restricted to Android O+, and there are no such devices in the waterfall yet (
- [Issue 763951](crbug.com/763951)). So when making changes you *must* check all the channel tests
+ [Issue 763951](https://crbug.com/763951)). So when making changes you *must* check all the channel tests
  pass on an Android O device locally.
 
 
@@ -118,4 +118,4 @@ each get a dedicated channel, within the 'Sites' channel group.
 ## Further reading
 
 - [Android notification channels documentation](https://developer.android.com/preview/features/notification-channels.html)
-- [Design doc for Clank notification channels](https://docs.google.com/document/d/1K9pjvlHF1oANNI8TqZgy151tap9zs1KUr2qfBXo1s_4/edit?usp=sharing)
\ No newline at end of file
+- [Design doc for Clank notification channels](https://docs.google.com/document/d/1K9pjvlHF1oANNI8TqZgy151tap9zs1KUr2qfBXo1s_4/edit?usp=sharing)

docs/cipd.md

@@ -214,7 +214,7 @@ assume that anything it installed is still installed, even if you deleted it.
 To clear the cache and force a full reinstallation, delete your
 `$GCLIENT_ROOT/.cipd` directory.
 
-Note that there is a [bug](crbug.com/794764) on file to add a mode to CIPD
+Note that there is a [bug](https://crbug.com/794764) on file to add a mode to CIPD
 that is not so trusting of its own cache.
 
 [1]: https://chromium.googlesource.com/infra/luci/luci-go/+/master/cipd/

docs/clang_static_analyzer.md

@@ -39,7 +39,7 @@ use_clang_static_analyzer = true
 The next time you run your build, you should see static analysis warnings appear
 inline with the usual Clang build warnings and errors. Expect some slowdown on
 your build; anywhere from a 10% increase on local builds, to well over 100% under Goma
-([crbug](crbug.com/733363)).
+([crbug](https://crbug.com/733363)).
 
 ## Supported checks
 Clang's static analyzer comes with a wide variety of checkers. Some of the checks

tools/mb/docs/design_spec.md

@@ -130,9 +130,9 @@ So:
    things are fast enough that we can afford to build everything affected by a
    patch, but listing every possible target explicitly would be painful. The
    GN Ninja generator provides an 'all' target that captures (nearly,
-   see [crbug.com/503241](crbug.com/503241)) everything, but unfortunately
-   GN doesn't actually represent 'all' as a meta target in the build
-   graph, so we will need to write code to handle that specially.
+   see [crbug.com/503241](https://crbug.com/503241)) everything, but
+   unfortunately GN doesn't actually represent 'all' as a meta target in the
+   build graph, so we will need to write code to handle that specially.
 
 7. In some cases, we will not be able to correctly analyze the build graph to
    determine the impact of a patch, and need to bail out (e.g,. if you change a