Code Quality: Collapse `Files.Package` project

[Lamparter]

Description

It's unnecessary to have a packaging project, since integrating the package into the code project is possible.

Concerned code

All of Files.Package

Gains

• Current method is unnecessary
• Makes more sense for consumer to set startup project as "Files.App"

Requirements

• Migrate AppX runtime files such as Package.appxmanifest/appxmanifest.xml to Files.App
• Enable MSIX deploy to Files.App project (...)

Comments

Not very high priority obviously...

[0x5bfa]

• Single packaging project doesn't support msixbundle deployment
• Moving the appxmanifest to another place would break the auto update mechanism (im still not sure how).

[Lamparter]

Moving the appxmanifest to another place would break the auto update mechanism (im still not sure how).

Really? Who said that..?

[yaira2]

The generated app installer path and file names are based on the packaging project name.

[Lamparter]

This should probably be marked as not planned.

[yaira2]

This should probably be marked as not planned.

We would probably do this if there were a way to generate msixbundles from a single project without relying on a script.