Add generic project resources copied into app bundles

Users should be able to add arbitrary read-only files, such as SQLite databases, JSON data, model files, templates, or other support assets, to an Objo project and have Studio copy those files into the built application's resources during Run, Build, Publish, and remote debugging.

This would cover the common Xojo-style workflow where a project has a resource folder and build steps copy selected files into the app bundle or distributable output. In Objo Studio, this should be a first-class project feature rather than a manual post-build step.

Expected user-facing behaviour:

• A project can contain a Resources tree for arbitrary files.
• Users can import files, import folders, drag files into the Resources tree, rename entries, delete entries, and organise them into folders.
• Resource files are stored inside the .objo project archive so builds do not depend on loose files beside the project.
• Build, Publish, normal Run, and remote debugging all deploy the same resources.
• ObjoBasic code has a stable way to locate the deployed resource root at runtime.