Update dependencies and remove unused ones. Pin git dependencies.

[ewanas]

OP#2200

---

Code Review Checklist

• Description accurately reflects what changes are being made.
• Description explains why the changes are being made (or references an issue containing one).
• The PR appropriately sized.
• New code has enough tests.
• New code has enough documentation to answer "how do I use it?" and "what does it do?".
• Existing documentation is up-to-date, if impacted.

[donpui]

Got warning on Android:

Warning: The plugin permission_handler_android requires Android SDK version 33.
For more information about build configuration, see https://docs.flutter.dev/deployment/android#reviewing-the-build-configuration.
One or more plugins require a higher Android SDK version.
Fix this issue by adding the following to /Users/donataspuidokas/Development/destiny/android/app/build.gradle:
android {
  compileSdkVersion 33
  ...
}

However it compiled and installed.

[donpui]

I have done smoke test on Windows, Android, Linux, Mac. Seems it works.

[meejah]

Whenever possible (i.e. in non-3rd-party repos) it'd be way better to actually tag things (then used named tags here).

[meejah]

can we do releases of these? or at least named tags (since they appear to be repos "we" control?)

[ewanas]

That's reasonable, I agree, CC @shareef-dweikat

I put the hashes here as an improvement over nothing at all. I guess also tags may be overwritten to point to different hashes. In that sense, maybe hashes are more reproducible?

[meejah]

Yeah, I guess depends what the use-case is ... for reproducibility I suppose the hash is better here (coming from python-land, you'd pin against "the hash of the 1.2.3 release on PyPI" normally).

Even if this uses the hash it could still be beneficial to have like "22.9.1" (date-based) tags to help the humans but I'll leave that to people actually doing this ;) and also I don't know flutter ecosystem at all

[ewanas]

Merging to allow testing early while intro_slider and expand_widget get updated(Looks like they are in need of getting some upstream updates as well as dependency updates) and also have a release or at least a tag, then will update those in another PR.

For window_size we will keep the hash as it is an external dependency.