Admit the per-line tag segment in the requests source pattern

[iderex]

Half of what Flowfin/jellyfin-plugin-requests#110 waits on, the half that is a file in this tree: sources/requests.json selects only the bare version convention today, so a release tagged under the one-version-many-lines decision (1.2.3.4-jf12-stable) would be published and never reach the manifest.

The pattern gains an optional per-line segment, probed both ways:

python -c "
import re
neu = r'^v?[0-9]+\.[0-9]+\.[0-9]+(\.[0-9]+)?(-jf[0-9]+)?(-stable)?$'
ok  = ['1.2.3','v1.2.3.4','1.2.3.4-stable','1.2.3.4-jf12-stable','1.2.3.4-jf13-stable','1.2.3.4-jf12']
bad = ['1.2.3-beta','1.2.3.4-jf12-beta','1.2-stable','1.2.3.4-stable-jf12','beta-1.2.3']
assert all(re.match(neu,t) for t in ok) and not any(re.match(neu,t) for t in bad); print('ok')
"
ok

The note in the file now names the line segment and where it came from. The channel still hangs on the tag convention, and the catalogue still separates lines by targetAbi - the segment only names which line a file came from. The second half of #110, shipping the first 12.0-line release, is the operator's tagging act and stays on that issue.