Updating wp versions blueprints

[fellyph]

Motivation for the change, related issues

This change expands the number of supported major WordPress versions for the wp parameter from the last four to the last six. I have looked at the folder packages/playground/wordpress-builds/src/wordpress, which contains those six versions.

Testing Instructions (or ideally a Blueprint)

1. Download the Branch
2. Install the project
3. Run the command npm run dev:docs
4. Navigate to the page wordpress-playground/blueprints/data-format
5. Check the new content listing the six last WordPress versions

[fellyph]

@adamziel, should we set a limit for supporting the last four major WordPress versions?

[adamziel]

Should we set a limit for supporting the last four major WordPress versions?

@fellyph I don't see much upside, and the downside would be breaking some existing Blueprints.

[fellyph]

@adamziel, we store the builds on the project, and some builds are as large as 28MB, which increases the total project's size.

[adamziel]

@fellyph While that's true, trunk is between 2GB and 3GB large. We can spare 28MB if that means not breaking existing Playground links. If the size of WordPress builds starts getting out of hand or becomes a significant percentage of the overall repository size, we can remove those builds then and look for a BC solution, e.g. fall back to fetching a full WordPress build from w.org.