[roll] Roll fuchsia [cm][trace_manager] Assign component id to trace_manager

trace_manager uses persistent storage to buffer traces before sending
them back to the host. As it's enabled in userdebug builds, it needs a
component id assigned to it.

Testing:
```
local/fuchsia2 ▶ ffx component show core/trace_manager
                 Moniker:  core/trace_manager
                     URL:  fuchsia-pkg://fuchsia.com/trace_manager#meta/trace_manager.cm
             Environment:  core-env
             Instance ID:  2e76933b4eb7ff47b2fd4abbd7c1aa5ec0ada042d88aa880d819cc9461e31572
         Component State:  Resolved
            Resolved URL:  fuchsia-pkg://fuchsia.com/trace_manager#meta/trace_manager.cm
                  Runner:  elf
                  ...
```

Original-Bug: 364894040
Original-Reviewed-on: https://fuchsia-review.googlesource.com/c/fuchsia/+/1272008
Original-Revision: ac464a13eb5dae3048a4a5231669f1a31c8c872b
GitOrigin-RevId: 563e767ceecca7a86f1c6a2934ec737388d90b6c
Change-Id: I2f838c33e48b6097bb092fbe1856e91ce74dd9ca
1 file changed
tree: b412b5279698a21f2963e3dc640f981aee98bcdb
  1. ctf/
  2. git-hooks/
  3. infra/
  4. third_party/
  5. flower
  6. jiri.lock
  7. MILESTONE
  8. minimal
  9. prebuilts
  10. README.md
  11. stem
  12. test_durations
README.md

Integration

This repository contains Fuchsia's Global Integration manifest files.

Making changes

All changes should be made to the internal version of this repository. Our infrastructure automatically updates this version when the internal one changes.

Currently all changes must be made by a Google employee. Non-Google employees wishing to make a change can ask for assistance in one of the communication channels documented at get involved.

Obtaining the source

First install Jiri.

Next run:

$ jiri init
$ jiri import minimal https://fuchsia.googlesource.com/integration
$ jiri update

Third party

Third party projects should have their own subdirectory in ./third_party.