chore: Prepare 3.0.0 release

[susnux]

3.0.0 - 2024-05-02

Breaking changes

Instead of also sanitizing the replacing variables, now only the result is sanitized, see pull request #648.

This will improve the performance if multiple placeholders are used and it allows this,
while the string is still sanitized:

t(
	`See {linkstart}documentation{linkend}`,
	{
		linkstart: '<a ...>',
		linkend: '</a>',
	},
	// No number
	undefined,
	{
		// Do not escape the result as we want the HTML anchor element
		escape: false,
	}
)

Added

• feat: export aliases t and n for translate and translatePlural

Fixed

• fix!: Only sanitize the result string when replacing variables

Changed

• Update NPM to latest LTS v10
• Migrate to vite for transpiling and vitest for testing
• chore: Added more tests for special cases on plural forms
• chore(deps): Bump tough-cookie to 4.1.3
• chore(deps): Bump postcss to 8.4.31
• chore(deps): Bump @nextcloud/typings to 1.8.0
• chore(deps): Bump dompurify to 3.1.1
• chore(deps): Bump @nextcloud/router to 3.0.1

[nickvergessen]

While I see the usecase, it's very problematic when a string contains 2 inputs that are user input 🙈
Maybe a second option would be better? 🤔

[susnux]

We can also add e.g. this API:

const userinput = '...'
t(
    'foo',
    '{a}link to {userinput}{end_a}',
    {
        a: {
            value: '<a>',
            escape: false,
        },
        end_a: {
            value: '</a>',
            escape: false,
        },
        userinput,
    },
)

Meaning options per placeholder