refactor: Content filter helper function

[ZhongpinWang]

Context

SAP/ai-sdk-js-backlog#202.

What this PR does and why it is needed

Deprecate buildAzureContentFilter() because it restricts filtering to have only one filter.

Implement ContentFilters.azure(). New filters can be added to ContentFilters constant.

[tomfrenken]

Concept looks good and even allows for adding streaming options.

LGTM, after making the adjustments Deeksha has requested.

[KavithaSiva]

Proposed API looks good to me too, although I didn't like it that the user has to explicitly wrap the calls inside an array even for using a single filter.

I feel typing { filters: [ContentFilters.azure({ Hate: 4, SelfHarm: 2 })] } to use a single filter is redundant.

An alternate I could think of was:

filtering: {
  input: ContentFilters.azure({ Hate: 4, SelfHarm: 0 }),
  // or
  input: ContentFilters.llamaGuard({ ... }),
  // or
  input: ContentFilters.addMultipleFilters(
    ContentFilters.azure({ Hate: 4, SelfHarm: 0 }),
    ContentFilters.llamaGuard({ ... })
  )
}

WDY think?
But yeah, the behaviour would then be similar to buildAzureContentFilter() and I would then think ContentFilters then only helps with discoverability.

[ZhongpinWang]

Proposed API looks good to me too, although I didn't like it that the user has to explicitly wrap the calls inside an array even for using a single filter.

I feel typing { filters: [ContentFilters.azure({ Hate: 4, SelfHarm: 2 })] } to use a single filter is redundant.

An alternate I could think of was:

filtering: {
  input: ContentFilters.azure({ Hate: 4, SelfHarm: 0 }),
  // or
  input: ContentFilters.llamaGuard({ ... }),
  // or
  input: ContentFilters.addMultipleFilters(
    ContentFilters.azure({ Hate: 4, SelfHarm: 0 }),
    ContentFilters.llamaGuard({ ... })
  )
}

WDY think? But yeah, the behaviour would then be similar to buildAzureContentFilter() and I would then think ContentFilters then only helps with discoverability.

I get your point. But as you mentioned, we then need some kind of ContentFilters.addMultipleFilters() function to concatenate filters, which feels just a bit of overkilling the problem and makes the helper function less helpful.

[KavithaSiva]

LGTM for me.

Agreed that the 2 import behaviors should be documented

But, @deekshas8 also wrote this, can you check with her what needs to be documented here?

Personally for me though I would prefer if the user always uses it via the ContentFilters for better discoverability of other functions too.

[KavithaSiva]

Some behaviour changes have been made to buildAzureContentFilter (The old convenience function). This has to be reverted as it's a breaking change.

[KavithaSiva]

Some behaviour changes have been made to buildAzureContentFilter (The old convenience function). This has to be reverted as it's a breaking change.

Done now.

Applied changes.