Finish overlord reorg to enable further work

[pedronis]

When we merged the reorg work in

https://github.com/snapcore/snapd/pull/3075

we had to undo some work toward the end to make it easier to cut 2.23.6:

undo commit

I would like to reapply the undo bits and finish that, so that can I proceed with changing how lock patterns for the snapstate handlers, a prereq for further work in

Improving the aliases implementation

Hello all, As a quick recap, aliases are that feature that allows people to declare more than one top-level command inside the snap instead of having available only the name of the snap itself. After some discussions and feedback from stakeholders, we’re changing the implementation of aliases a bit so that it’s a bit more intuitive in a few places. Here is how it is going to differ from what we have in place today: Users are now in control In the current implementation users cannot add alias…

any objections?

As a reminder: this will moves handlers out of snapmgr.go into handlers.go! any pending PR with changes in that area will need to fix the conflict

[zyga-snapd]

Since we have a release branch for 2.23.6 (release/2.23) I think we can just do it. The only remark would be that if future changes conflict they should be targeting 2.23 release branch directly rather than being a cherry pick from a squashed master branch.

[niemeyer]

Sounds good to me as well.

[pedronis]

@niemeyer @mvo proposed https://github.com/snapcore/snapd/pull/3107 with this.

[pedronis]

@pstolowski this is now merged, probably conflicts with your config PR

[pstolowski]

@pedronis Indeed. I’ve fixed the conflicts, PR #3070 should be good again now.