[device_info] Port device_info to use platform interface

[yash1200]

Description

In this PR, I have ported device_info to use device_info_platform_package .

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.

• 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 (flutter analyze) does not report any problems on my PR.
• I read and followed the Flutter Style Guide.
• The title of the PR starts with the name of the plugin surrounded by square brackets, e.g. [shared_preferences]
• I updated pubspec.yaml with an appropriate new version according to the pub versioning philosophy.
• I updated CHANGELOG.md to add a description of the change.
• 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 (please indicate a breaking change in CHANGELOG.md and increment major revision).
• No, this is not a breaking change.

[yash1200]

Hey @ditman , kindly have a look at this one. 😄

[ditman]

LGTM! Let's merge this once the tests pass!

[yash1200]

Thank You Sir!

[yash1200]

Hey @ditman , if I were to add support for linux in device_info , then what are the necessary stats that I must include in it. Should I include all the stats which neofetch shows?

[ditman]

@yash1200 I'm not a desktop expert. Maybe @stuartmorgan has a better idea. I'd say: start with the stats that you need for your app, and build up from there.

[stuartmorgan]

I'm not sure there's really any way for me to answer that question; even with just two implementations (iOS and Android) there's almost nothing at all in common between the two, so it's hard to judge what is or is not in scope. Perhaps before extending this to N new platforms there should be a clearer articulation by the ecosystem team of what general criteria should be used to decide what is added to it.

(This PR is probably not the place for that discussion though.)

[stuartmorgan]

Filed flutter/flutter#64569