resolveExternalFields shouldn't search for fields #843
Description
Spotted in: #840 (comment)
It doesn't seem to be a big issue if we consider only "integration" type packages, but it appears to be a problem when we consider "input" type packages. The current logic "knows" where fields can be found (<package_root>/fields or <package_root>/data_stream/<data stream name>/fields) and it "globs" them there.
It seems to be a better idea if field locations are provided externally.