False positives in "function M:F/A is not exported" warning

[jcpetruzza]

Describe the bug
Using a recent development version of OTP, erlc is emitting warnings when calling functions that don't exist, and some of those are incorrect.

To Reproduce

• Example 1: On behaviour modules, behaviour_info/1 is not recognized:

$ cat beh.erl
-module(beh).
-export([go/0]).
-callback foo() -> ok.
go() -> ?MODULE:behaviour_info(callbacks).

$ erlc beh.erl
beh.erl:4:10: Warning: function beh:behaviour_info/1 is not exported
%    4| go() -> ?MODULE:behaviour_info(callbacks).
%     |          ^

• Example 2: Default values in record definitions inside a header file are not recognized if used before being exported:

$ cat blah/blah.erl
-module(blah).
-record(blah_rec, {
    foo = blah:f() :: integer()
}).
-export([f/0, g/0]).
f() -> 42.
g() -> #blah_rec{}.

$ erlc blah.erl
blah/blah.erl:3:11: Warning: function blah:f/0 is not exported
%    3|     foo = blah:f() :: integer()
%     |           ^

This case happens often when blah_rec is defined in a header file that will also be included from other applications.

Expected behavior
No warning should be reported in these examples. In particular, this breaks builds that treat all warnings as errors.

Affected versions
Happens on a recent master: b4af22d