fix(template): avoid treating table-prefixed custom elements as table tags

[liweijie0812]

Summary

Fix table tag detection in createContents so it only matches real table-related tags when the tag name is followed by whitespace, >, or /.

Problem

The previous regex could incorrectly match custom element names that start with a table tag name.

example：

html`<thead-element></thead-element>`
Before this change, <thead-element> could be treated as if it started with <thead>, because the regex matched the thead prefix.
Fix
Add a lookahead after the table tag group:
(?=[\s>\/])
This ensures matches like <thead>, <thead class="x">, and <thead/> still work, while <thead-element> does not match as a table tag.

[smalluban]

Thanks for your contribution. The fix looks great!

[smalluban]

Please update the code, so the linter check passes.

[liweijie0812]

Please update the code, so the linter check passes.

done

[coveralls]

coverage: 99.957%. remained the same — liweijie0812:fix/table-tag-signature-regex into hybridsjs:main

[liweijie0812]

When will a bug fix be released?