Don't auto-close paths when using Graphics with CanvasRenderer (#4997) ...

When defining a path, any call to beginFill results in the path being closed,
but only for the Canvas renderer, not for the WebGL renderer.
This commit removes the check that sets the shape to be closed when a fill is
active. This unifies the rendering behavior between Canvas and WebGL.

CanvasRenderer tint could affect bounds calculation (#5028)

Fix Graphics.lineStyle jsdoc (#5026) ...

The default alignement value is 0.5, not 1.

Adds Graphics adaptive calculation of quadratic curve and arc subdivision (#4658)

VAO leak in Mesh and Graphics (#4893)

Added stroke alignment property to lineStyle (#4886) ...

No allows you to specify if a line is inner or outer aligned. 0 =
inner, 1 = outer, 0.5 = middle (default)

Adds `drawStar` method to Graphics (#4612)

Graphics drawPolygon: (#4191) ...

* update documentation -- method also accepts a PIXI.Polygon

fix(Graphics): exclude holes in Graphics#containsPoint (#3976) ...

* fix(GraphicsRenderer): fix graphics render with fill and line when nativeLines=true

* fix(GraphicsRenderer): fix eslint and jsdoc

* fix(Graphics): exclude holes in Graphics#containsPoint

Fixes the padding for Graphics (#4020)

Improvements to how and what is stored in the texture caches. (#3834) ...

* Improvements to how and what is stored in the texture caches.
Built upon the good work from https://github.com/pixijs/pixi.js/pull/3789
+ For Text, the base textures were in the BaseTextureCache, but textures weren't in the TextureCache. This has been fixed
+ Now able to tell the BaseTexture the origin of where the canvas being passed through has come from. ie. was it from the text class? was it from the graphic class? was it from caching as a bitmap? More information now to track where these canvases (canvii??) have been generated from
+ BaseTexture has addBaseTextureToCache and removeBaseTextureFromCache functions, to match regular Texture. Any adding or removing to the BaseTextureCache is now through these functions

! Breaking change. When you call Texture.fromTextureFromCache - it no longer automatically removes it's base texture from the base texture cache. Not sure how people feel about this

? I don't like lines 233 to 236 in Texture.js, and line 591 in BaseTexture.js - I don't see why they are there or why they are needed, but I chickened out on removing them!

* Renaming function to more generic names

* Adding deprecation layer

* Fixed trying to add texture to BaseTexture cache causing unit test fail

* Fixed reading from the wrong cache

* Able to remove textures and base textures from their caches via object instances
Added debug warning if trying to add a texture to a cache id that already exists
Added unit tests

* Default string for texture origin

* Different object creation style

* textureCacheId is now an array of potential entries

* textureCacheId changed to textureCacheIds

* Removed unneeded string creation

Read `texture` via `_texture` directly in sprite (#3780) ...

* Use `*._texture.*` directly in Sprite.js

It could offer a bit little performance gains.
And  read texture via `_texture` is a common way/style in  PIXI.js

* Update CanvasTinter.js

* Update DisplacementFilter.js

* Update Graphics.js

[v4.4] fix SpriteRenderer for multiple webgl renderers, fix tests, add "withGL" (#3758) ...

* fix SpriteRenderer for multiple webgl renderers, fix tests, add "withGL"

* isWebGLSupported renamed to withGL

Fast rect blendMode problem (#3707) ...

* fast rect blendMode. Tested.

* add webgl-only test
add test for rgb2hex
fix problem in rgb2hex

add nativeLines option for Graphics (#3328)

Fix for generateCanvasTexture() #3446 (#3605)

Improved documentation of the destroy method (#3529) ...

* Improved documentation of the destroy method
Documents the .texture and .baseTexture parameters for the settings object that may not be used for the class itself, but could get propogated down to children
Fixes https://github.com/pixijs/pixi.js/issues/3407

* Improved clarity of docs

Update `clear` for a more thorough cleaning (#3445) ...

* Update `clear` for a more thorough cleaning

Clear something that should be cleared.
`
        this.currentPath = null;
        this._spriteRect = null;
`
if no this patch , some test cases will be failed.


##Test Case
There is some common codes of test cases :
```js
var renderer = new PIXI.WebGLRenderer(900, 600, {
    clearBeforeRender: false,
    backgroundColor: 0xFFFFFF
});
document.body.appendChild(renderer.view);

// the root container.
var stage = new PIXI.Container();
```

### TEST 1
If no  ```currentPath = null ``` ,  the second arc can't be rendered, and there is no error on browser's console.

```js

    var graphics = new PIXI.Graphics();
    stage.addChild(graphics);

    // clear manually
    renderer.clear();

    graphics.clear();
    graphics.beginFill(0xFF0000);
    graphics.arc(150, 160, 100, 0, Math.PI * 2, false);
    graphics.endFill();

   // draw  the first shape
    renderer.render(stage);

    graphics.clear();
    graphics.beginFill(0x0000FF);
    graphics.arc(150+50, 160+50, 100, 0, Math.PI * 2, false);
    graphics.endFill();

   // draw  the second shape
    renderer.render(stage);
```

### TEST 2
If no  ```_spriteRect = null ``` ,  the first rect can't be rendered, and there is no error on browser's console.

```
    var graphics = new PIXI.Graphics();
    stage.addChild(graphics);

    // clear manually
    renderer.clear();

    graphics.clear();
    graphics.beginFill(0xFF0000);
    graphics.drawRect(150, 160, 100, 60);
    graphics.endFill();

    // draw the first shape
    graphics.updateTransform();
    graphics.renderWebGL(renderer);

    graphics.clear();
    graphics.beginFill(0x0000FF);
    graphics.drawRect(150+50, 160+50, 100, 60);
    graphics.endFill();

    // draw the second shape
    graphics.updateTransform();
    graphics.renderWebGL(renderer);

    // flush manually
    renderer.flush();
```

### Summary

If don't call  `graphics.clear();` before draw the second shape , there will be another error.

If add 
```
        this.currentPath = null;
        this._spriteRect = null;
```
in `clear()` everything will be OK, and I test many other examples, this patch doesn't break anything else, it's safe.


I know when we want to draw multi shapes , we could use multi graphics objects.
But we shouldn't prevent users to use one shared graphics to draw multi shapes.

* Remove trailing spaces.

Test case & fix for Graphics._calculateBounds calling updateLocalBounds every time (#3444) ...

* Test case for #3414

* Fixes #3414

* fixed expectation

Graphics - getLocalBounds after generateCanvasTexture (#3398) ...

* added graphics.getLocalBounds expectation

* fixes #3274

add comments and change test description

fix/graphics: get points for newly created shape (#3433)

Merge pull request #3290 from pixijs/master ...

Merge master -> dev

Fix anticlockwise sweep calculation (#3249) ...

* Fix anticlockwise sweep calculation

* Simplify sweep calculation

* Sweep typo

get rid of trigonometric stuff. ...

Explanation: sinTheta*w is actually dy, cosTheta*w is actually dx.

switch to arctan2

needs absolute value

fixes #3168

lint fixes

fixes #2824