major: new Osm_Project application

[osmianski]

Problem

A typical Osm Framework-based project contains several applications:

• Osm_App is the main application that you eventually host on the Web.
• My_Samples is a superset of Osm_App used in unit tests. It may contain additional modules that are only used in tests.
• Osm_Tools is an auxiliary application used to develop and manage the main application.

Each application has intimate knowledge about its modules and classes.

However, in some cases, it's useful to introspect all modules and classes of the project regardless to which application they belong. It is especially useful in code generation.

Solution

It's written in present tense, as if the change is already implemented, on purpose. It makes it easier to update the framework documentation with new features.

New Osm_Project application allows to introspect all modules and classes of
the project regardless to which application they belong.

Use it as follows:

use Osm\Project\App;
...

$result = [];

Apps::run(Apps::create(App::class), function (App $app) use (&$result) {
    // use $app->modules and $app->classes to introspect 
    // all modules and classes of the projects and its 
    // installed dependencies
    
    // put the introspection data you need into `$result`. Don't reference
    // objects of the `Osm_Project` application, as they'll won't work 
    // outside this closure. Instead, create plain PHP objects and arrays, 
    // and fill them as needed 
});

Notice. This application is for introspection only. Invoking user code in context of this application may produce unexpected results.

[osmianski]

It's a major change, all projects should compile the Osm_Project app in
the gulpfile.js:

global.config = {
    'Osm_Tools': [],
    'Osm_Project': [], // NEW
    'Osm_App': ['_front__tailwind']
};