Module Namespace Exotic Objects are incorrectly typed as if they have an Object prototype

<!-- 🚨 STOP 🚨 𝗦𝗧𝗢𝗣 🚨 𝑺𝑻𝑶𝑷 🚨 Half of all issues filed here are duplicates, answered in the FAQ, or not appropriate for the bug tracker. Even if you think you've found a *bug*, please read the FAQ first, especially the Common "Bugs" That Aren't Bugs section! Please help us by doing the following steps before logging an issue: * Search: https://github.com/Microsoft/TypeScript/search?type=Issues * Read the FAQ: https://github.com/Microsoft/TypeScript/wiki/FAQ Please fill in the *entire* template below. --> <!-- Please try to reproduce the issue with `typescript@next`. It may have already been fixed. --> **TypeScript Version:** 3.5.3 <!-- Search terms you tried before logging this (so others can find this issue more easily) --> **Search Terms:** - import hasOwnProperty - import star hasOwnProperty - namespace exotic object - import prototype **Code** ```ts import * as Foo from "./Foo" if (foo.hasOwnProperty("bar")) { console.log(foo.bar) } ``` **Expected behavior:** Type error due to `hasOwnProperty` not existing, as the ["module namespace exotic object" should have a `null` prototype](https://tc39.es/ecma262/#table-29). **Actual behavior:** Code runs producing runtime error that `hasOwnProperty` is `undefined`.