fix bbox as per spec

[omeid]

Summary

As per the spec, bbox should not include any transformations, including scaling. It should also not include any control points. This fixes getBBox to give correct results matching Google Chrome, Firefox as per the spec.

• What issues does the pull request solve? Please tag them so that they will get automatically closed once the PR is merged

• What is the feature? (if applicable)
  Bug fix.

• How did you implement the solution?
  Like this, see.

• What areas of the library does it impact?
  getBBox API.

Test Plan

I build some stuff that works with SVG, the results on web were inconsistent, and digging down I realise it was a react-native-svg.

Some fun fact, there was a surprisingly similar bug related to very confusing named (CGPathGetBoundingBox vs CGPathGetPathBoundingBox) APIs as well.
https://bugzilla.mozilla.org/show_bug.cgi?id=1369904

What's required for testing (prerequisites)?

What are the steps to reproduce (after prerequisites)?

Compatibility

OS	Implemented
iOS	✅
Android	✅
Web	🔘 *

• Depends on the host platform. But works fine in major browsers.

Checklist

• I have tested this on a device and a simulator
• I added documentation in README.md
• I updated the typed files (typescript)
• I added a test for the API in the __tests__ folder

[omeid]

cc @msand

Since you have laid out the initial work for this.