[upnp]: add all KODI supported real subtitle formats when act as a DLNA render

[ihipop]

upnp: add all KODI supported real subtitle formats when act as a DLNA render
and share the white list with the KODI DLNA server

Description

• KODI support work as a DLNA media render with the supported format of subtitle
• KODI has a builtin subtitle white list almost 10 years ago in year 2013, which is obviously outdated
• KODI has another builtin similar subtitle white list, which is maintained actively
• this PR makes them share the white list and keep the white list of DLNA media render up to date

Motivation and context

Reading :

• https://emby.media/community/index.php?/topic/111848-dlna-configuration-profile-error/&do=findComment&comment=1188987
• https://emby.media/community/index.php?/topic/112866-dlna-subtitle-index-is-ignored-by-dlna-plugin-1089/&do=findComment&comment=1189227
  EMBY can "DLNA" a movie along with all it's subtitle to KODI
  But, the white list of subtitle of DLNA media render is outdated
  so KODI will reject all the subtitle not in the list,such as ass/ssa
  which makes the subtitle function broken

How has this been tested?

• as a DLNA render:

local build pass and tested with emby dlna server,all subttitles functional

• as a UPNP/DLNA server:

local build pass and tested with Bubble upnp app

• ENV

Distributor ID:	ManjaroLinux
Description:	Manjaro Linux
Release:	22.0.0
Codename:	Sikaris

What is the effect on users?

user will have a full functional subtitle selection when play video by supported DLNA control point

Screenshots (if appropriate):

Types of change

• Bug fix (non-breaking change which fixes an issue)
• Clean up (non-breaking change which removes non-working, unmaintained functionality)
• Improvement (non-breaking change which improves existing functionality)
• New feature (non-breaking change which adds functionality)
• Breaking change (fix or feature that will cause existing functionality to change)
• Cosmetic change (non-breaking change that doesn't touch code)
• None of the above (please explain below)

Checklist:

• My code follows the Code Guidelines of this project
• My change requires a change to the documentation, either Doxygen or wiki
• I have updated the documentation accordingly
• I have read the Contributing document
• I have added tests to cover my change
• All new and existing tests passed

[enen92]

Thanks a lot for the contribution and for fixing this. Left a few comments where I think this can be improved

[enen92]

Thanks! Please squash the commits

[enen92]

Thanks will be merged once jenkins gets green

[ihipop]

Thanks will be merged once jenkins gets green

did jenkins is building against wrong commit?

[enen92]

Thanks will be merged once jenkins gets green

did jenkins is building against wrong commit?

It's building a merge commit of yours on top of the master head commit:
dd37b9b