[i18n] Unexpected behaviors

[rafaelss95]

Description and reproduction of the issue

1. boundTextAllowedPattern isn't behaving as expected. See this case:
   

   angular-eslint/packages/eslint-plugin-template/tests/rules/i18n.test.ts

   Lines 204 to 215 in b434b51

   	convertAnnotatedSourceToFailureCase({
   	description: 'it should fail because of the custom pattern',
   	annotatedSource: `
   	<div>
   	<span>-{{data_from_backend}}</span>
   	~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
   	</div>
   	`,
   	messageId: i18nText,
   	options: [{ boundTextAllowedPattern: '-' }],
   	data: { attributeName: 'span' },
   	}),

Here we report a bound text that starts with an allowed character. It should be valid instead;

2. Missing i18n-* attributes are reported duplicately. See this case:

angular-eslint/packages/eslint-plugin-template/tests/rules/i18n.test.ts

Lines 167 to 178 in b434b51

	{
	messageId: i18nAttribute,
	line: 8,
	column: 11,
	data: { attributeName: 'label' },
	},
	{
	messageId: i18nAttribute,
	line: 8,
	column: 11,
	data: { attributeName: 'label' },
	},

3. Report ranges could be more assertive. For example, when an i18n attribute is missing an id or the text is missing the i18n attribute, the whole element is reported, when we just need to report the original attribute or text;

4. <ng-template> , ngPlural, ngPluralCase and ngProjectAs should be ignored;

5. Numeric values and HTML entities ("i18n": [false,"check-text"] fails on text containing only non-word characters mgechev/codelyzer#618 and [template-i18n]: Single HTML entities should be ignored mgechev/codelyzer#952) should be ignored. Examples:

<div ariaselected="0"></div>
<div matBadge="&#8288;">5</div>
<div>732</div>
<div>&nbsp;</div>

6. ICUs are not being reported (https://angular.io/guide/i18n#translate-plurals-and-alternate-expressions);

7. Duplicate custom IDs are not being reported (https://angular.io/guide/i18n#define-unique-custom-ids).