Add OGF for Azure Functions Apps that use the Dependency Injection Feature.

#### What problem would the feature you're requesting solve? Please describe.
Customers may follow our guidance and use IFunctionsConfigurationBuilder to add configuration sources.
They may also not follow our guidance at all and overwrite or add configuration in another way.
If it's the latter then they could be broken by changes in the Functions Host unintentionally.

#### Describe the solution you'd like
1. Add an OGF for the recommended IFunctionsConfigurationBuilder approach.
2. Add additional OGF's to cover other ways of adding configuration Sources.

Ensure these apps start up and can connect to bindings\triggers and the Storage account as appropriate.

#### Describe alternatives you've considered
I can't see any alternatives at present.

Start by locating existing OGF coverage for Azure Functions Apps and the recommended IFunctionsConfigurationBuilder approach. Exercise both the recommended and alternative configuration-source paths, then verify that apps start, connect to bindings and triggers, and reach the Storage account as appropriate.

Written by the indexing model from the issue text.