make direction optional in portProps schema

[shehaban]

• Updated the direction field in portProps to be optional instead of required.
• This allows ports to be defined without explicitly specifying a direction

🎯 Why this change is needed

• The direction field is already optional in the core portProps.
• This change keeps the schema consistent while refactoring to use portProps from @tscircuit/props instead of declaring it inside core.
• Prevents validation mismatches during the migration.

[seveibar]

can you explain why?

[shehaban]

@seveibar I’m working on the core to use portProps from the props instead of defining it inside the core. It was previously defined as optional in corePortProps.

[seveibar]

Why does it need to be optional? Why not make required

[shehaban]

Because making it required will break existing tests, around 300 snapshot tests will fail
Keeping it optional avoids breaking current snapshots.

[MustafaMulla29]

Because making it required will break existing tests, around 300 snapshot tests will fail Keeping it optional avoids breaking current snapshots.

Nothing will break it's a required property.

[shehaban]

It was optional in core, and I moved it as it was