Update transport model creation for new class structure

[GDYendell]

No description provided.

[hyperrealist]

I think everything looks good, but just one thought: should we rename the base Transport class to BaseTransport or something like that?

FastCS/src/fastcs/transport/transport.py

Line 10 in e944113

class Transport:

Because it is placed earlier in the hierarchy than the actual transports it could be a bit confusing to new users.

from fastcs.transport import BaseTransport
# vs
from fastcs.transport.epics.ca.transport import EpicsCATransport

This will stylistically align with other parts of the codebase like BaseController too. Perhaps needs more consideration.

[GDYendell]

should we rename the base Transport class to BaseTransport

Yeah it is something to consider. Though the reason BaseController exists currently is because Controller and SubController inherit it, so it is not quite the same. But, it might be a bit nicer if we have BaseTransport and then useTransport as the union of all transports for the model generation. I will leave it as is for now.