Update getRanges to use pod or nexus

- dawg
    - /customer/languages uses pod because it's profile data
    - /customer/likes uses pod because it's profile data
    - getLogs uses nexus because they're stored centrally
    - /links/type uses nexus because there's no pid in the base. Tested this
      one, but I don't know what it's supposed to do and I only get empty
      responses.
- lib/entries runBases uses pod because these bases have pids. When they don't,
  pod falls through to nexus anyway, so this is the safe choice.
- facebook/posting uses pod because this is a person's profile. Tested locally.
- webservice /by/contact: I assume this is supposed to be posts by the contact,
  but I get `[]` both locally and in prod. This change makes sense and doesn't
  alter behavior.
- scripts/clearProfile: Updated to use pod, since these are profile bases

Left alone scripts/backlog because it's run centrally, but if we change it, it
should talk to nexus.