Fix falcon dispatcher detection

[kaylareopelle]

In our environment report, the falcon dispatcher is not being identified.

According to @prateeksen, the code never reaches this line

[workato-integration]

https://new-relic.atlassian.net/browse/NR-295896

[prateeksen]

@kaylareopelle I have done a little more digging and found that find_class_in_object_space method returns nil until the ::Falcon::Server class is actually loaded into the object space and server is started. And the twist here is that, by the time this class is loaded into object space, and find_class_in_object_space returns :falcon Environment report is already sent from the agent from here with nil value in dispatcher in environment report.
I tried to return :falcon without checking this if condition, but in that case agent's worker thread is not initiated and that got initiated when I fired a curl request on application.
Could you please look into it from here, why the agent's worker not initiated without calling find_class_in_object_space

[kaylareopelle]

Hi @prateeksen, thanks for digging in! I'll take a look this week as part of my hero duties.

[kaylareopelle]

Hi @prateeksen, what's the priority on this issue? I think we may need to include it in our regular planning cycle to make meaningful progress.

[prateeksen]

Hi @kaylareopelle This is comparatively low priority than #2777.