Let requirejs name the popover plugin instead of explicitly naming it.

Phil, this was the simplest solution I could come up with, possibly also the most maintainable. I dislike the fact that the nice short descriptive module name bites the dust, but such is life. This bug in requirejs persists even in the latest version (I tested it) so this workaround is really the only option right now).

Explicitly naming the popover plugin appears to trigger a race condition that
results in a namespace conflict. The issue appears to be that there is both
a directory named popover and a module named popover. The browser loads the
modules asynchronously. If the popover module has finished loading by the time
math, image or link loads, nothing bad happens. If the popover module has not
finished loading, it attempts to load it again, finds the popover directory
and attempts to load lib.js in that directory, resulting in a 404 error. By not explicitly naming
the popover module, it will be named popover/popover-plugin automatically,
which in turn resolves the namespace issue.