Warning about non-HTTP functions with SWA when using backend with Azure Functions Core tools

Before filing this issue, please ensure you're using the latest CLI by running `swa --version` and comparing to the latest version on [npm](https://www.npmjs.com/package/@azure/static-web-apps-cli).

**Are you accessing the CLI from the default port `:4280` ?**

- [ ] No, I am using a different port number (`--port`) and accessing the CLI from that port
- [x] Yes, I am accessing the CLI from port `:4280`

> Make sure you are accessing the URL printed in the console when running `swa start`!

**Describe the bug**
Redundant warning shown when manually starting api

**To Reproduce**
Steps to reproduce the behavior:

1. Create a backend including both http triggers non-HTTP triggered functions
2. Launch SWA backend with "bring your own", api using Azure Functions Core Tools as per documentation [instructions](https://azure.github.io/static-web-apps-cli/docs/use/api-server)
3. See a warning in console `Function app contains non-HTTP triggered functions. Azure Static Web Apps managed functions only support HTTP functions. To use this function app with Static Web Apps, see 'Bring your own function app'`

**Expected behavior**
No error message as the backend/api is managed outside of SWA