fix: missing support for enrichOptions

[davilima6]

Purpose

Add support for enrichOptions parameter to the Content API, allowing users to control the depth level of reference enrichment when fetching content.

Approach and changes

• added enrichOptions property with enrichLevel and model support to GetContentOptions type
• implemented enrichOptions query parameter handling for /query and /content endpoints

Testing instructions

1. Create a @builder.io/sdk test script
2. Run getAll() method with enrichOptions:

   await builder.getAll('some-model-with-nested-references', {
     noTraverse: false,
     enrich: true,
     enrichOptions: {
       enrichLevel: 3,
       model: {
         'model1': {
           fields: 'id,data.field1,data.field3',
         },
         'model2': {
           fields:
             'data.id,data.field1,data.field2,data.field6',
         },
         'model3': {
           fields: 'data.and,so,on'
         },
       },
     },
     fields: 'data.rootField1,data.rootField2,data.rootField3',
     limit: 100,
     query: {
       'data.field': 'some value',
     },
   })
   

3. Confirm the underlying API call includes enrich=true, enrichOptions.enrichLevel=3 and enrichOptions.model.model1=id,data.field1,data.field3 query parameters

[changeset-bot]

⚠️ No Changeset found

Latest commit: 337dc87

Merging this PR will not cause a version bump for any packages. If these changes should not result in a new version, you're good to go. If these changes should result in a version bump, you need to add a changeset.

This PR includes no changesets

When changesets are added to this PR, you'll see the packages that this PR includes changesets for and the associated semver types

Click here to learn what changesets are, and how to add one.

Click here if you're a maintainer who wants to add a changeset to this PR