[FEATURE] Separate RegisterModelStep into RegsiterRemoteModelStep and RegisterLocalModelStep

[joshpalis]

Is your feature request related to a problem?

Currently our RegisterModelStep is attempting to parse fields for both registering a local model and registering a remote model (link). In order to identify optional fields and enforce required fields, it is necessary to separate the step into RegisterLocalModelStep and RegisterRemoteModelStep

What solution would you like?

The RegisterLocalModelStep should have the following required fields (API Documentation):

• name
• version
• model_format
• model_group_id
• model_content_hash_value
• model_config
• url

The model_config field is a JSON object which includes the following fields :

• model_type - required
• embedding_dimension - required
• framework_type - required
• all_config - optional field that contains all model configurations

The RegisterRemoteModelStep should have the following fields (API Documentation)

• name
• function_name
• model_group_id
• description
• connector_id OR connector

The connector_id field is just a string which is provided by the create connector API. However, there is an option to define an inline connector configuration (internal connector API documentation), which contain all the required Create Connector API fields