internal/router: return 404 on meta/any with no includes

When we requested metadata on a fully qualified id using meta/any
with no includes, it would succeed unconditionally.

A better fix would be to make meta/any with no includes return an
error, but we can't do that without compromising the existing GUI client.

As drive-by fixes, we make the bulk id handler work correctly when
there are some ids are not found, and the error message from
the any handler return the full name of the meta endpoint requested.