[platform_interface] 1145 removed optional timestamp

[TimHoogstrate]

Resolves enhancement: 1145, by removing the optional permission timestamp from the platform interface.

Pre-launch Checklist

• I made sure the project builds.
• I read the Contributor Guide and followed the process outlined there for submitting PRs.
• I updated pubspec.yaml with an appropriate new version according to the pub versioning philosophy, or this PR is does not need version changes.
• I updated CHANGELOG.md to add a description of the change.
• I updated/added relevant documentation (doc comments with ///).
• I rebased onto main.
• I added new tests to check the change I am making, or this PR does not need tests.
• I made sure all existing and new tests are passing.
• I ran dart format . and committed any changes.
• I ran flutter analyze and fixed any errors.

[codecov]

Codecov Report

All modified and coverable lines are covered by tests ✅

Files	Coverage Δ
...or_platform_interface/lib/src/models/position.dart	100.00% <100.00%> (ø)

📢 Thoughts on this report? Let us know!.

[JeroenWeener]

Could you explain why this change is necessary? In your earlier comment you explain why the timestamp should be nullable.

#1145 (comment)

[mvanbeusekom]

Could you explain why this change is necessary? In your earlier comment you explain why the timestamp should be nullable.

#1145 (comment)

We have discussed this off-line. The reason the timestamp is nullable is because in old versions the Position class was also used to represent positions resolved using geocoding. However since version 6.0.0 support for geocoding has been moved out of the geolocator plugin and into it's own plugin (geocoding).

Since the Position class now only represents positions acquired from the the geolocation services provided by the device (GPS, Network, etc...) a timestamp should always be included and therefore there is no need to keep it optional.

[mvanbeusekom]

LGTM