feature(uvc): Applied proprietary changes in UVC Device class

[roma-jam]

Requirements

• Fixed uninitialized values during streaming negotiation parameters
• Added VIDEO_CS_ITF_VS_FORMAT_FRAME_BASED support

Limitations

N/A

Breaking change

No breaking changes

Testing:

• After applying changes the esp-video-components/esp_video/examples/uvc could be built successfully:

*NOTE: Modified component usb_device_uvc was used to enable possibility to use espressif/tinyusb component by local path.

Checklist

• Pull Request name has appropriate format (for example: "fix(dcd_dwc2): Resolved address selection when several phy are present")
• Optional: README.md updated
• CI passing

Related issues

• Changes applied also in synchronization commit: Upstream synchronization  #43
• Resolves fix: espressif/esp-video-components@6e61b6f#diff-f742676e9225ab4ba99adff463cfe58296bb400490cc0e4f5c635567e6be634d
• Upstream PR: feat(uvc): support format frame based hathach/tinyusb#2656

[tore-espressif]

Can be closed in stead of hathach#2656 ?

[tore-espressif]

@roma-jam Can we merge hathach/master to our espressif/release/v0.17 first? And then proceed with this PR?

If possible, we want to stay as close to upstream as possible, so it is not complicated to upgrade (like when we upgraded from 0.15 to 0.17)

[roma-jam]

Sure, we can.
I have created upstream synchronization PR for release/v0.17: #43

We can merge it and then return back to the current PR (but in the end only the variables initialization will left in here).

[roma-jam]

The upstream synchronization #43 dropped one commit: support format frame based.
Only fix uninitialized value is left.