fix(frontend): advanced-toggle-default

[Abhi1992002]

• resolve Hide "advanced" toggle on blocks if there are no advanced inputs #8739

I don't think so that this is a frontend issue [might be wrong] , because if we are not classifying that a particular input is advanced = true/false. Then we automatically get advanced = True.

[netlify]

✅ Deploy Preview for auto-gpt-docs-dev canceled.

Name	Link
🔨 Latest commit	df65229
🔍 Latest deploy log	https://app.netlify.com/sites/auto-gpt-docs-dev/deploys/6746aea3524b6e0008ff5241

[netlify]

✅ Deploy Preview for auto-gpt-docs ready!

Name	Link
🔨 Latest commit	df65229
🔍 Latest deploy log	https://app.netlify.com/sites/auto-gpt-docs/deploys/6746aea30fa4140008a51cb7
😎 Deploy Preview	https://deploy-preview-8802--auto-gpt-docs.netlify.app
📱 Preview on mobile	Toggle QR Code... Use your smartphone camera to open QR code link.

---

To edit notification comments on pull requests, go to your Netlify site configuration.

[Pwuts]

If it works for other blocks, then could you check why the toggle isn't working on the GithubPullRequestTriggerBlock?

[Abhi1992002]

If it works for other blocks, then could you check why the toggle isn't working on the GithubPullRequestTriggerBlock?

To make it work, we need to explicitly set advanced = False in both the event and the trigger.

similar to this

 value: Any = SchemaField(
            default=None,
            description="The value for the new entry.",
            placeholder="new_value",
            advanced=False,
        )
        
entries: dict[Any, Any] = SchemaField(
            default={},
            description="The entries to add to the dictionary. This is the batch version of the `key` and `value` fields.",
            advanced=True,
        )