Tracking service: initial prototype with fused location

[wonder-sk]

• service does not run in a separate process anymore
• using FLP to get location
• seems to track well even with screen turned off

to-do:

• make the code more robust & finish things
• test with various android versions
• maybe record track to a file anyway, to prevent data loss? (commit the recorded track on app restart)
• better android notification - regularly update tracking time and distance
• use or don't use fused provider for tracking consistently with what positionkit uses

things to fix at some point:

• after switching back to the app while tracking, the PositionKit's location may be old for a couple of seconds, and the tracking line may end with one long segment towards this outdated location, confusing the user. maybe we should update PositionKit's location from the latest tracked point
• after switching back to the app after tracking for a longer time (at least a couple of minutes), the screen may stay black for a few seconds before showing things - maybe processing delayed track points?

[github-actions[bot]]

Pull Request Test Coverage Report for Build 9459719669

Details

• 0 of 0 changed or added relevant lines in 0 files are covered.
• 50 unchanged lines in 2 files lost coverage.
• Overall coverage decreased (-0.008%) to 59.922%

---

Files with Coverage Reduction	New Missed Lines	%
input/core/merginuserinfo.cpp	3	73.76%
input/app/activeproject.cpp	47	68.87%
<!--	Total:	50		-->

Totals
Change from base Build 9455523246:	-0.008%
Covered Lines:	7670
Relevant Lines:	12800

---

💛 - Coveralls