fix: remove preprocessor-specific attributes

[dummdidumm]

• global for style tags
• src for script/style tags

fixes #652

@dominikg does this fix the v-p-s issue?

Before submitting the PR, please make sure you do the following

• It's really useful if your PR relates to an outstanding issue, so please reference it in your PR, or create an explanatory one for discussion. In many cases features are absent for a reason.
• This message body should clearly illustrate what problems it solves. If there are related issues, remember to reference them.
• Ideally, include a test that fails without this PR but passes with it. PRs will only be merged once they pass CI. (Remember to run pnpm lint!)

Tests

• Run the tests with npm test or pnpm test

[dominikg]

this example does not make sense as i assume potato-language uses the lang attribute value.

If you want to show it here, the preprocessor would have to use a custom potato attribute that then gets filtered

[dominikg]

should this be a generic util?

export const filterAttributes(attributes: Record<string,any>, filterFn: (a:string) => boolean) {
  return Object.fromEntries(Object.entries(attributes).filter(([a])=>filterFn(a)))
}

usage:

const cleanAttributes = filterAttributes(attributes, a => a !=='src');
// or
const attributesToRemove = ['foo','bar'];
const cleanMultipleAttributes = filterAttributes(attributes, a => !attributesToRemove.includes(a))

that can be reused for global and potentially others?