feat: support dot-path namespace names

[SoundMatt]

Closes #93

Summary

A namespace name containing dots (e.g. name: com.example.vehicle) is now expanded to the equivalent nested structure at parse time:

# These two files now produce identical ASTs:

# dot-path form
namespaces:
  - name: com.example.vehicle
    methods:
      - name: start

# explicit nesting
namespaces:
  - name: com
    namespaces:
      - name: example
        namespaces:
          - name: vehicle
            methods:
              - name: start

Implementation

_expand_dot_namespace() is added to ifex_parser.py and called from get_ast_from_yaml_file() immediately after dacite.from_dict(). It recursively processes the namespace tree, splitting any dot-path name into nested Namespace objects. All content (methods, properties, events, structs, typedefs, enumerations, interface, child namespaces) is moved to the innermost namespace; intermediate layers are empty containers.

Since all generation tools share the same parser entry point, they all benefit automatically without individual changes.

Tests

tests/test_dot_path_namespace/ contains:

• dotpath.ifex / nested.ifex — equivalent YAML fixtures
• test_dot_path_namespace.py — three test cases:
  1. Full three-part dot path produces same namespace tree as explicit nesting, with content in innermost
  2. Plain (non-dot) namespace names are unchanged
  3. Unit test of _expand_dot_namespace() directly for a two-part path