feat: flet doctor CLI command

[Gordon-Burns]

Description

Test Code

# Test code for the review of this PR

Type of change

• Bug fix (non-breaking change which fixes an issue)
• New feature (non-breaking change which adds functionality)
• Breaking change (fix or feature that would cause existing functionality to not work as expected)
• This change requires a documentation update

Checklist

• I signed the CLA.
• My code follows the style guidelines of this project
• I have performed a self-review of my own code
• I have commented my code, particularly in hard-to-understand areas
• My changes generate no new warnings
• New and existing tests pass locally with my changes
• I have made corresponding changes to the documentation (if applicable)

Screenshots

Additional details

Summary by Sourcery

New Features:

• Introduce the flet doctor command to diagnose potential issues with the Flet environment.

[CLAassistant]

All committers have signed the CLA.

[Gordon-Burns]

Tests passed and screenshot of output attached - Ready for review

[ndonkoHenri]

Thanks for your contribution! It's awesome.

Will have a look at it today and return to you asap.

[ndonkoHenri]

• Running flet doctor -v shows the following (we have twice thesame info):
  

• Also, seems like the output is printed all at once, which takes a while. I will suggest we print info step by step like in the flet build command (where we make use of rich's status) or flutter doctor:
  

[Gordon-Burns]

Thanks @ndonkoHenri I have solved the duplicate and print issues as well as adding some additional checks in the verbose option

[ndonkoHenri]

Great! Thanks for the changes @Gordon-Burns.

Some other remarks:

• Can you please remove all the lines printing strings containing "==" ? And also "Detailed check completed" at the end. Let's please solely have the important output of the command being printed out.
• In your methods (ex: check_flet_version, check_os_info), no need to return a value as it won't be used. Then in the handle method we can just call the different methods, without having to store them in variables.

[Gordon-Burns]

@ndonkoHenri Picked this up over the weekend and have addressed feedback by removing the unnecessary characters. Also changed the check_vitrual_env as it did not account for someone using conda

[Gordon-Burns]

@ndonkoHenri Just wanted to check in if there are anymore changes required or if this request is good ?

[FeodorFitsner]

Re: "Flutter is not installed" on the last screenshot - in Flet 0.26.0 flet build is installing Flutter SDK, JDK and Android SDK if they are not installed. Other words, we are not asking/encouraging users to install those anymore. I don't know if it makes sense for flet doctor to check/warn on that. What do you think?

[Gordon-Burns]

Hi @FeodorFitsner the issue asked for this to be included in the checks- but if you feel it's no longer needed I am happy to remove?

[FeodorFitsner]

Thanks. I think it could be safely removed. Flet does no longer rely on Flutter installed by the user, but uses its private install.

[Gordon-Burns]

Sure, I will pick this up over the weekend and push changes

[Gordon-Burns]

@FeodorFitsner , Thanks again for the feedback this has now been addressed and pushed

[ndonkoHenri]

Sorry @Gordon-Burns, got distracted/occupied by some other stuffs lately.

I made some last modifications as you might have noticed: the admin privileges are non-important, and it's check has been removed.

Your PR looks good to be merged - thanks again for picking this up!

[Gordon-Burns]

Thanks @ndonkoHenri no worries on removing the other function