fix: adding module to export

[orest-tokovenko-block]

Fixes reportPrivateImportUsage warnings for downstream consumers importing the auto-generated models from vantage_sdk.models.

Problem

vantage_sdk/models/__init__.py does from .gen_models import * and then declares its own explicit __all__ listing only the hand-written .common models. Per the Python typing spec, an explicit __all__ overrides wildcard re-export and becomes the authoritative public interface. The generated models (Folder, CreateFolder, CreateCostExportSchema, UpdateVirtualTagConfig, etc.) are therefore treated as private re-exports, so consumers get warnings like:

"Folder" is not exported from module "vantage_sdk.models"
  Import from ".folder" instead (reportPrivateImportUsage)

This only affects third-party py.typed consumers, so it does not surface in this repo's own CI.

Fix

• Import the gen_models module by name so its export list is referenceable
• Append gen_models.__all__ to the package __all__ so the generated models are part of the public interface

from . import gen_models
...
__all__ += gen_models.__all__

No runtime or logic change: the wildcard already binds the names, the .common overrides still win, and overlapping names are harmless duplicates in __all__. The __all__ += module.__all__ form is used because it is statically recognized by pyright and does not trigger reportUnsupportedDunderAll (folded ] + ...) or ruff RUF005 (unpacking).

Validation

Reproduced in a clean environment with a non-editable py.typed wheel:

• Before: 4 reportPrivateImportUsage warnings
• After: 0 warnings

Repo ruff, ruff format, and basedpyright checks remain green.