Add missing extractor for staticmesh product type

[moonyuet]

Changelog Description

This PR is to add missing fbx extractor for staticMesh product type and also use staticMesh as product type instead of unrealStaticMesh to align with the unreal workflow to other dccs

Additional info

We need to discuss the use case of this product type in Unreal to other DCCs

Testing notes:

1. Select Asset and create staticmesh instance
2. Publish

[LiborBatek]

@moonyuet should the testing include the new unrealasset template when testing this PR? or not neccessary atm? thx

[moonyuet]

@moonyuet should the testing include the new unrealasset template when testing this PR? or not neccessary atm? thx

@LiborBatek no need to include that template. it would use the existing unreal template instead.

[LiborBatek]

Gives me following error when trying to Publish:

Traceback (most recent call last):
  File "C:\Users\lbate\AppData\Local\Ynput\AYON\dependency_packages\ayon_2406251801_windows.zip\dependencies\pyblish\plugin.py", line 528, in __explicit_process
    runner(*args)
  File "c:\Work\REPO\ayon-unreal\client\ayon_unreal\plugins\publish\extract_fbx.py", line 35, in process
    task.set_editor_property('object', asset_names)
TypeError: AssetExportTask: Failed to convert type 'str' to property 'Object' (ObjectProperty) for attribute 'object' on 'AssetExportTask'
  TypeError: NativizeProperty: Cannot nativize 'str' as 'Object' (ObjectProperty)
    TypeError: NativizeObject: Cannot nativize 'str' as 'Object' (allowed Class type: 'Object')

[LiborBatek]

Now Publish of staticMesh goes well and also loading it back seems fine!

small note: when published staticMesh loaded back into UE it has no same amount of shader slots but just one (matter of FBX options?? when producing that staticMesh?)

but other than that works well: