LWC OmniOut Issues

[Dm1tryKarpenko]

Hi Vlocity Team!
I tried to use LWC OmniOut Command, but faced some problems.

I did a little research on the lwcOmniOutRetrieve.js code, this is what I found.

I have an OmniScript with Type__c = "b2bExpressCLM" and Language__c = "Multi-Language".
When trying to request LWC components from the salesforce, it composes the DeveloperName field LightningComponentBundle of the object to request.

const currentOmniScriptLwc = await fetchOmniOutContents (record [vlocity.namespace + '__Type__c'] + record [vlocity.namespace + '__SubType__c'] + record [vlocity.namespace + '__Language__c'], vlocity);

We get the name "b2bExpressCLMgenerateProposalDocumentLWCMulti-Language"
(Please pay attention to dash)

According to the documentation, DeveloperName may contain only underscores and alphanumeric characters.
https://developer.salesforce.com/docs/atlas.en-us.api_tooling.meta/api_tooling/tooling_api_objects_lightningcomponentbundle.htm

Component has DeveloperName = "
b2bExpressCLMGenerateProposalDocumentLWCMultiLanguage "
As a result, I can not get the component because the DeveloperName is set incorrectly

Another problem is when an attempt is made to receive a component that is in the manage package.
For example, we get dependencies

listOfCustomLwc = await extractLwcDependencies (JSON.parse (prefilledJson) || {});

in the resulting list, items will be with a namespace prefix, for example "vlocity_cmt__clmSelectableItems", but the DeveloperName database will be stored without a prefix. As a result, I again cannot get the component.

[AllanOricil]

@rutlabaga Is this fixed? If not I think I can solve it in one of the tickets I have at work, and later I can open a PR here.