[Bug]: VS Code msssql object explorer isnt showing container tables like Azure SQL DB

### Description

VS Code is not 100% compatible with the Azure SQL DB container - msdb, tempdb, and model are showing up in the database list. Attached is screenshot.

Earlier discussions indicated that this may be related to SMO/Object Explorer classification behavior.

Spec: https://microsoft.sharepoint.com/:w:/t/Ad-Astra/cQoJjFD0402xSYkN9WyNjcsyEgUC4BeSRpG-XAE7U4e8ND3QxQ

### Steps to Reproduce

### Affected Area

- [ ] Connection dialog (SQL Server | Azure browse/Fabric browse)
- [ ] Query editor
- [ ] Query results panel
- [x] Object Explorer
- [ ] GitHub Copilot integration
- [ ] Preview/Edit data
- [ ] Table Designer
- [ ] Schema Designer
- [ ] Schema Compare
- [ ] Local SQL Server Container provisioning
- [ ] SQL database in Fabric provisioning
- [ ] DACPAC/BACPAC export/import
- [ ] SQL Database projects
- [ ] Query Plan Visualizer
- [ ] Other (please describe below)

### If you selected "Other", please describe the affected area

_No response_

### Environment Information

mssql extension

### Confirmation

- [x] I have searched existing issues and couldn't find a match
- [ ] I want to work on this issue

Start by reproducing the issue in the Object Explorer against an Azure SQL DB container, then review the SMO/Object Explorer classification behavior referenced in the issue and the linked specification. Done means the database list and container tables are shown consistently with Azure SQL DB behavior, including the handling of msdb, tempdb, and model.

Written by the indexing model from the issue text.