docs: clarify documentation for getLastCrashReport

[codebytere]

Description of Change

Resolves #17399.

At present, it's not clear that getLastCrashReport only returns crash reports that have been uploaded, and so this PR add clarifying information to documentation.

Checklist

• PR description included and stakeholders cc'd
• npm test passes
• tests are changed or added
• relevant documentation is changed or added
• PR title follows semantic commit guidelines
• PR release notes describe the change in a way relevant to app developers, and are capitalized, punctuated, and past tense.

Release Notes

Notes: Clarified usage of crashReporter.getLastCrashReport() in documentation.

[MarshallOfSound]

This is a pretty harsh rename that serves no purpose other than to help explain what the method does slightly better.

Can we at a minimum deprecate this so that it still works in the next major and preferably just support both Forever ™️ . It's not like adding getLastCrashReport() { return this. getLastUploadedCrashReport() } is going to be much of a maintenance burden 👍

[codebytere]

hmm, i agree; if we think that just being really explicit in the documentation would address the same root problem then i'm happy with that tbqh

what do you think @MarshallOfSound?

[MarshallOfSound]

@codebytere Adding explicit docs would be way better for both newcomers to the API and reducing the churn on existing users 👍

[codebytere]

@MarshallOfSound updated!

[release-clerk]

Release Notes Persisted

Clarified usage of crashReporter.getLastCrashReport() in documentation.

[trop]

I have automatically backported this PR to "5-0-x", please check out #17493

[trop]

I have automatically backported this PR to "4-1-x", please check out #17494