[Resolver] use just left and top, and remove transform, from processes

[oatkiller]

Summary

• position nodes w/ just left and top, instead of left, top, and transform.
• Remove padding on resolver map. the raster size measuring code doesn't account for this.
• Remove constant (+10) from node position expression. As it's not being multiplied against the projection matrix, it won't scale
• Remove unused variables

Summarize your PR. If it involves visual changes include a screenshot or gif.

Checklist

Delete any items that are not applicable to this PR.

• Any text added follows EUI's writing guidelines, uses sentence case text and includes i18n support
• Documentation was added for features that require explanation or tutorials
• Unit or functional tests were updated or added to match the most common scenarios
• This was checked for keyboard-only and screenreader accessibility
• This renders correctly on smaller devices using a responsive layout. (You can test this in your browser
• This was checked for cross-browser compatibility, including a check against IE11

For maintainers

• This was checked for breaking API changes and was labeled appropriately

[kibanamachine]

💚 Build Succeeded

• continuous-integration/kibana-ci/pull-request
• Commit: cfca50a

To update your PR or re-run it, just comment with:
@elasticmachine merge upstream

[elasticmachine]

Pinging @elastic/endpoint-app-team (Feature:Endpoint)

[bkimmel]

❔ It seemed a little more intuitive to me to keep the calculated value of left and top for the element aligned with the left and top but I guess it doesn't change anything material about the way it lays out, so if you like this better go for it.

[bkimmel]

❔ A lot of these style rules were set to meet design's guidance via the mocks and signed off by them. You tested to make certain this doesn't alter what they've signed off on?

[oatkiller]

sorry, but we can't support having a padding w/o adjusting the logic that measures the size of the resolver map.