Show candidate functions at the beginning of the scan #3
Description
Right now the exposed functions are filtered based on which modules they are associated with. For instance a function that is only associated with https://developer.atlassian.com/platform/forge/manifest-reference/modules/scheduled-trigger/ isn't scanned, since that wouldn't make sense. Ideally the list of candidate functions should be shown with which type of scan is run on them or if they're skipped.