Add class to pull the devices current battery %.

Add ktlint static analysis, this can be added either via the plugin or a new Gradle file.
Once ktlint is added to the project, the github actions file should be updated, to ensure that it runs on CI as well.

This will require #2 to be merged before it can be completed.

It would be good if the app had dark theme support based on the users' OS settings.

This can be achieved by following the Material Design guidelines for Android. Once the correct theme is set in the styles.xml the system will handle most of the work. Although view elements will need to have the correct elevation to ensure they have the correct colour.

Currently, the app has the default FAB included with an envelope icon. The app should be updated to make use of the FAB or it should be removed.

The FAB could be used to share information about the device with other apps.

This task could potentially be split up.

Add a class to get the basic information about a handset, this being the information mainly in the Build class.
Information provided would ideally be something like
"Manufacturer Name" to "Samsung"
"Device Name" to "S9+"

We should be able to pull down the model name of the handset, so something akin to "S9Plus" could be retrieved, likely from the Build class.

We could pull a list of connected displays (main phone display and any connected external and virtual displays) and grab some of their properties, such as width, height, refresh rate

We need to set up an initial structure in the application, so that it is easy to add more ways to get device information down the line.

We can use this issue to discuss the structure, unless somebody is really sure they have a good way to go about it.

To make it easier to get the required dependencies in all the various areas, and setup any classes correctly, we should integrate some form of dependency injection into the project. The earlier this is integrated the easier it will be going forwards. My personal suggestion is Dagger, maybe using Hilt to see how that works, but I think other frameworks like Koin could work as well.

Add Detekt static analysis to the project, https://github.com/detekt/detekt.
Once it is added to the project, the github actions file should be updated to ensure that it runs on CI as well.

This will require #2 to be merged before it can be completed.

Instead of using Groovy, we could write them in Kotlin and see how they work.