[META] issues found with 0.3.0 pre-release test

[J-ZhengLi]

Issues to fix before releasing 0.3.0

• 1. CLI component selection (linux组件选择优化 #136) still not fixed, and the default selections are not shown

Issues to fix before releasing 0.3.1 0.4.0 (because there are some api level changes, the next update won't be a patch update anymore)

• 1. GUI/CLI detailed log does not appears when running rustup when installing toolchain (fix an issue causing rustup & cargo's output not appearing until the end of execution #159)
• 2. GUI available toolkit list does not filtering out the one that are already installed (fix an issue causing the available toolkits not filtering the one that are already installed & correcting component version display when updating #158)
• 3. GUI when selecting a toolkit to update, the component list shows toolchain components with version stable v1.82.0 causing it be detected always as the newest version (fix an issue causing the available toolkits not filtering the one that are already installed & correcting component version display when updating #158)
• 4. GUI when the user click uninstall after clicking update, the progress starts at 100, and the detailed log carried over from last update step, also no detail log of the current uninstall steps are shown. (fix an issue where the logger could send log to closed channel in manager mode #175 )
• 5. CLI when updating toolkit, there's no version record for installed tools, causing them not being selected as update candidates (improve fingerprint.toml, allow it to store tool's kind and version #167)
• 6. CLI when trying to update the toolkit but no update availablle, the manager tool should tells the user that the version of current toolkit is already the latest (display toolkit version when user attempting to update from latest toolkit #160)
• 7. GUI/CLI when downloading rustup-init, the download function does not take system proxy into account, causing a failed to download rustup error It was not proxy issue, it was because it got blocked by restricted network
• 8. CLI manager on windows has no pause and still requires to be open with cmd or powershell (Windows CLI 模式需要优化 #139)(improve manager cli #170)