Allow creation of Dataverse tables in a non-default solution context (not only the Default Solution)

Allow creation of Dataverse tables directly inside a chosen solution (instead of Default Solution)

Description

When creating a new Dataverse table, the current experience forces the table to be created inside the Default Solution, with no clear option to select a custom solution. This causes ALM issues because tables created outside a specific solution do not automatically belong to that solution, making them harder to track, version, export, and deploy across environments.

Proposed Improvement

• Add the ability to choose the target solution when creating a new Dataverse table.
• Ensure table metadata (columns, relationships, forms, views) is automatically created inside the selected solution.
• Update SDK/API support to allow specifying the target solution when creating tables programmatically.
• Provide documentation that promotes solution-aware table creation as part of recommended ALM practices.

Why This Matters

• Prevents pollution of the Default Solution with unmanaged components.
• Ensures tables use the correct publisher prefix tied to the solution.
• Supports predictable ALM, CI/CD pipelines, and environment migrations.
• Aligns with Microsoft’s recommendation to build everything inside solution-aware contexts.

No files, tests, or entry points are identified. Start by locating the table-creation flow and the SDK/API surface, then determine how solution context is represented. Done should include solution-aware creation for table metadata and the requested documentation, with behavior verified in the repository's available tests.