Reducing noise for metadata logging

[aishwaryabh]

Issue describing the changes in this PR

The host and worker metadata providers can be checked in parallel due to GetFunctionMetadata being called in the FunctionMetadataManager. After stepping through the code, I saw that the function gets called twice, once when we set includeCustomProviders to false and the second time when includeCustomProviders is set to true. We don't want to log how many functions have been loaded after we log how many have been found.

Here's how the logging looked like before:

[2023-07-25T23:22:43.607Z] Loading functions metadata
[2023-07-25T23:22:43.607Z] Reading functions metadata
[2023-07-25T23:22:43.626Z] 1 functions found
[2023-07-25T23:22:43.628Z] 0 functions loaded

And here is what the logging looks like now:

[2023-07-25T23:22:43.607Z] Loading functions metadata
[2023-07-25T23:22:43.607Z] Reading functions metadata (Custom)
[2023-07-25T23:22:43.626Z] Reading functions metadata (Custom)
[2023-07-25T23:22:43.628Z] 0 functions loaded

resolves #9420

Pull request checklist

• My changes do not require documentation changes
  • Otherwise: Documentation issue linked to PR
• My changes should not be added to the release notes for the next release
  • Otherwise: I've added my notes to release_notes.md
• My changes do not need to be backported to a previous version
  • Otherwise: Backport tracked by issue/PR #issue_or_pr
• My changes do not require diagnostic events changes
  • Otherwise: I have added/updated all related diagnostic events and their documentation (Documentation issue linked to PR)
• I have added all required tests (Unit tests, E2E tests)

Additional information

Additional PR information

[liliankasem]

Don't forget to also update the change log!

[mathewc]

I've been seeing these extraneous logs and have wondered where they were coming from. Good to clean this up since it's confusing during log investigations