Probably best to give eroman a chance to weigh in on naming before writing a CL.

The current name seems OK to me.

The interface is pretty close to https://chromium.googlesource.com/chromium/src/+/master/net/proxy_resolution/proxy_resolver.h, but with some extra dependencies used specifically for running PAC.

Given that a "proxy resolver" is already a well established term in the codebase, I would say it is better to keep close to that than to use new nomenclature like "pac executor".

If we really wanted to clarify, could call it PacProxyResolver to emphasize that it is a for PAC. Or keep it as ProxyResolver, but rename the dependencies to include the word PAC in them.

Note that external consumers will need an API to map a GURL to a proxy...I'd call that "proxy resolution".

Also, "ProxyResolutionService" vs "ProxyResolver" seems very non-intuitive naming.  One would think they do the same thing.