Smarter matches using product's versioning system

[Mpdreamz]

Added a lot more logging too:

content-source match elastic/elasticsearch 9.1

info ::e.d.c.a.a.tSourceMatch:: NO speculative build 9.1 is lte product current '9.2.0'
info ::e.d.a.c.atchingService:: 'elastic/elasticsearch' '9.1' combination not found in configuration.

::set-output name=content-source-match::false
::set-output name=content-source-next::false
::set-output name=content-source-edge::false
::set-output name=content-source-current::false
::set-output name=content-source-speculative::false

assembler content-source match elastic/elasticsearch 9.2

nfo ::e.d.c.a.a.tSourceMatch:: Current is not using versioned branches checking product info
info ::e.d.c.a.a.tSourceMatch:: Speculative build 9.2 is gte product current '9.2.0'

::set-output name=content-source-match::true
::set-output name=content-source-next::false
::set-output name=content-source-current::false
::set-output name=content-source-edge::false
::set-output name=content-source-speculative::true

assembler content-source match elastic/docs-content 9.2

info ::e.d.c.a.a.tSourceMatch:: No versioning system found for elastic/docs-content on 9.2
info ::e.d.a.c.atchingService:: 'elastic/docs-content' '9.2' combination not found in configuration.

::set-output name=content-source-match::false
::set-output name=content-source-next::false
::set-output name=content-source-edge::false
::set-output name=content-source-current::false
::set-output name=content-source-speculative::false

New repositories will always build for integration branches:

assembler content-source match elastic/unknown 9.2

info ::e.d.c.a.a.tSourceMatch:: Repository elastic/unknown has not yet been onboarded into assembler.yml
info ::e.d.c.a.a.tSourceMatch:: Speculatively building elastic/unknown since it looks like an integration branch

::set-output name=content-source-match::true
::set-output name=content-source-next::false
::set-output name=content-source-current::false
::set-output name=content-source-edge::false
::set-output name=content-source-speculative::true

[reakaleek]

Hmmmm.. I also noticed this in one of my PRs. hmmm