API Calibration: pkg/heapdump_intrumentation

[Notification (via Tables by Area 120)]

Dear API council members,

fdu...@google.com has requested that the following API be added to the Fuchsia SDK: pkg/heapdump_intrumentation

As such, it's time for an async API Calibration! This will give the API owner one last round of feedback before the API is shared with partners, and therefore harder to update.

Please provide feedback on fxrev.dev/870445 within the next 7 days!

Note that this calibration is not gating. Any feedback provided during this calibration is just "food for thought." Once the calibration is done, it's up to fdu...@google.com and the Diagnostics owner(s) to decide what changes to make to the API, if any.

More information:

API Area: Diagnostics
API Reviewers: crj...@google.com migue...@google.com
Guide doc (if any):
Notes: This library talks to the heapdump collector package only, using the fuchsia.memory.heapdump.process.Registry protocol (which is never exposed to the library user). Since the heapdump collector package will be distributed in the SDK too, there is no need to make the protocol versioned, as both the library and the package will always be updated at the same time. More context in this thread: https://groups.google.com/a/fuchsia.dev/g/api-council/c/G5TtqttZ76s

You can find up-to-date information on this calibration request here: https://tables.area120.google.com/table/atU1DkOE7LbbE5ZwElU_NH/row/8XUGjFFco1I3uveBZoUkR_?utm_source=bot&utm_medium=email

Sincerely,
The API Council Bot

[Notification (via Tables by Area 120)]

API council members: this is the last call for comments on fxrev.dev/870445!

Please add any remaining feedback by the end of the day. If you've looked at the library and had no feedback, say so on the changelist!

[Notification (via Tables by Area 120)]

This concludes the API Calibration for pkg/heapdump_intrumentation!

fdu...@google.com, your next steps are:
1. Mark fxrev.dev/870445 as "Abandoned", so it remains as a record of this API calibration.
2. Coordinate with your API reviewer(s) to determine which suggestions from the calibration period to incorporate into your API.
3. Make those changes.
4. Send your API reviewer(s) a CL that changes your API's `sdk_category` to the desired value.
5. Reply to this email, letting everyone know your API made it into the SDK!

Thank you for your contribution to Fuchsia's API surface!