fix(crashlytics): parameter information accepts Iterable<Object> for further diagnostic logging information

[russellwheatley]

Description

Updated recordError so it now allows Iterable<Object in the information parameter. This makes it backwards compatible, but also allows users to pass in whatever object they wish (e.g. ['something', 'version']) and it will write it to a String for logging in the Crashlytics dashboard in release mode.

I've tested in release mode using this input:

final err = Exception('AAAAAAAA');
Iterable<Object> properties = ['in release mode'];
FirebaseCrashlytics.instance.recordError(err, StackTrace.current,
    information: properties, fatal: true);

It shows on the dashboard correctly:

Related Issues

fixes #7912

Checklist

Before you create this PR confirm that it meets all requirements listed below by checking the relevant checkboxes ([x]).
This will ensure a smooth and quick review process. Updating the pubspec.yaml and changelogs is not required.

• I read the Contributor Guide and followed the process outlined there for submitting PRs.
• My PR includes unit or integration tests for all changed/updated/fixed behaviors (See Contributor Guide).
• All existing and new tests are passing.
• I updated/added relevant documentation (doc comments with ///).
• The analyzer (melos run analyze) does not report any problems on my PR.
• I read and followed the Flutter Style Guide.
• I signed the CLA.
• I am willing to follow-up on review comments in a timely manner.

Breaking Change

Does your PR require plugin users to manually update their apps to accommodate your change?

• Yes, this is a breaking change.
• No, this is not a breaking change.

[russellwheatley]

Hey @kevinthecheung, I have another small doc update if you could take a look, please? Thanks.