Update state boundaries from NE to include statistical boundaries.

[zerebubuth]

Include Admin-1 statistical boundary and Admin-1 statistical meta bounds as types of state boundary.

Connects to #797.

This was (somewhat surprisingly) the only migration I needed to run to get the tests to pass. Since this is on top of the v0.10.0 tag, will we tag the pre-merge state as v0.10.1? If so, then it should already be covered by the existing migrations in the repo, but the shorter version is:

update ne_10m_admin_1_states_provinces_lines
set mz_boundary_min_zoom = mz_calculate_min_zoom_boundaries(ne_10m_admin_1_states_provinces_lines.*)
where featurecla in ('Admin-1 statistical boundary', 'Admin-1 statistical meta bounds');

@rmarianski could you review, please?

[rmarianski]

👍

Since other code has landed on master since, should we make a v0.10 release branch off the v0.10.0 tag, and merge this change into there? And then we can merge the release branch into master?

[zerebubuth]

ea43400 is a commit on top of v0.10.0, so we could just tag it v0.10.1 if we want to?

[rmarianski]

ea43400 is a commit on top of v0.10.0, so we could just tag it v0.10.1 if we want to?

👍 This is what I'll do.

Do we want to make a separate pr on top of this commit (ea43400) to include a v0.10.1 changelog entry and tag that? Or do we not bother and just add in a changelog entry on master?

[rmarianski]

pr for the changelog entry.