Add daprTriggers to those that don't require storage

I wonder if we're better at this point to only enforce `AzureWebJobsStorage` if it's a timer trigger or event hub trigger rather than today how we allow-list certain ones. Regardless we are now launching 3 new triggers that don't require a storage account that the core tools block today:

`daprBindingTrigger`
`daprServiceInvocationTrigger`
`daprTopicTrigger`

// @anthonychu @ConnorMcMahon

Start by locating the core-tools allow-list that blocks daprBindingTrigger, daprServiceInvocationTrigger, and daprTopicTrigger when AzureWebJobsStorage is absent. Check how existing non-storage triggers are handled and identify the relevant tests, then verify that all three Dapr triggers are accepted without storage while storage-dependent triggers remain enforced.

Written by the indexing model from the issue text.