refactor(all): Remove all manual dependency_overrides

[spydon]

Description

Manual dependency_overrides in the examples shouldn't be needed since Melos already should handle those.

Checklist

• I read the Contributor Guide and followed the process outlined there for submitting PRs.
• I titled the PR using Conventional Commits.
• I did not modify the CHANGELOG.md nor the pubspec.yaml files.
• All existing and new tests are passing.
• The analyzer (flutter analyze) does not report any problems on my PR.

Breaking Change

Does your PR require plugin users to manually update their apps to accommodate your change?

• No, this is not a breaking change.

[vbuberen]

Unfortunately it doesn't solve the problem I mentioned in #1619 (comment) because it is not about using overrides, but because melos version bumps version of share_plus_platform_interface and during melos publish dry run can't resolve the bumped version of platform interface for share_plus.
There were a few mentions that the problem is about some changes in pub and it is not Melos related.

I have tried your PR with additional similar change in share_plus you did, but haven't seen any changes in behavior during melos bootstraping, etc.
Additionally I would prefer to have dependencies from path in example apps as really use Melos only when need to do release, not during work on plugins.

[spydon]

Makes sense that it didn't solve anything then.

Additionally I would prefer to have dependencies from path in example apps as really use Melos only when need to do release, not during work on plugins.

You still have to run Melos bootstrap to work locally though, and then it would set up the examples to be dependent on the other packages in the repository?

[vbuberen]

You still have to run Melos bootstrap to work locally though, and then it would set up the examples to be dependent on the other packages in the repository?

No, I don't. I started to use Melos only recently and only for purpose of publishing. Before that just opened a project of a plugin in question and work on it.

[spydon]

No, I don't. I started to use Melos only recently and only for purpose of publishing. Before that just opened a project of a plugin in question and work on it.

Interesting, how do you work with changing packages that are dependent on other packages in the repository, like the interfaces for example? Because if you haven't run melos bootstrap it would pull the interface package from pub instead of using the local one?

[vbuberen]

Interesting, how do you work with changing packages that are dependent on other packages in the repository, like the interfaces for example?

Probably, I haven't bumped into this case so far 🤷🏻

[spydon]

@vbuberen should I close this or do you want to start using melos all the way? :)

[vbuberen]

Well, let's merge it if Melos takes care of this stuff during versioning, but don't really see much benefits.

[spydon]

@vbuberen something strange had happened when this branch was updated with main, but it's fixed now. The auto-complete was cancelled though.

[vbuberen]

Yeah, had to manually restart some of our flaky android integration tests, but now everything seems fine.