Switch from camelCase to snake_case

[vcschapp]

Description

Brief description of the business purpose and effect of the pull request.

This commit switches properties and enumerators from camelCase naming to snake_case naming throughout the schema.

The purpose is to improve compatibility with SQL-based tools. Because SQL uses case-insensitive identifiers for historical reasons, SQL-based tools cause problems and information loss with camel-casing because they tend to treat all identifiers as if they were alllowercase or ALLCAPS.

In the Overture Schema Task Force meeting of 2024-02-07, the task force decided to adopt the snake_case proposal. The proposal originated in Jake's Schema Friction discussion document on the Overture Confluence.

While we believe that snake_case is slightly unconventional and, dare I (Vic) say also more unsightly in the JSON context, we feel that for SQL compatibility reasons, the pros of changing outweigh the cons.

Reference

List of relevant links to GitHub issues, PRs, and other documentation.

1. https://github.com/OvertureMaps/schema-wg/issues/272
2. https://wiki.overturemaps.org/x/SQGAAQ

Testing

Brief description of the testing done for this change showing why you are confident it works as expected and does not introduce regressions. Provide sample output data where appropriate.

1. Updated examples and counterexamples and ensured all tests pass.
2. In some cases improved the counterexamples by fixing longstanding bugs and adding the ext_expected_errors property to introduce some basic assertion sanity.
3. Verified that the Docusaurus docs build and did a quick search through them for identifiers needing to be fixed.

Checklist

Checklist of tasks commonly-associated with schema pull requests. Please review the relevant checklists and ensure you do all the tasks that are required for the change you made.

1. Add relevant examples.
2. Add relevant counterexamples.
3. Update in-schema documentation using plain English written in complete sentences, if an update is required.
4. Update Docusaurus documentation, if an update is required.
5. Review change with Overture technical writer to ensure any advanced documentation needs will be taken care of, unless the change is trivial and would not affect the documentation.

Documentation Website

Update the hyperlink below to put the pull request number in.

Docs preview for this PR.

[jenningsanderson]

🎉 Provided it passes validation and the docs build, let's get this merged down onto dev so we can continue building on top of it.

[jwass]

Looks like some class enum values in land and landuse still need to be converted.

[vcschapp]

Looks like some class enum values in land and landuse still need to be converted.

Thanks for finding that. Fixed in my latest update.