Fieldstone compatibility with REEID Translate

Plugin capabilities

• Stores Fieldstone field values in dedicated, indexed database tables (one row per post) rather than only using `wp_postmeta`.
• Maintains a postmeta mirror (enabled by default) so other WordPress ecosystem components that expect postmeta can still access values; includes a rebuild tool for both directions.
• Provides a visual editor to define field groups, including custom post types and taxonomies, with location rules that target where groups appear (e.g., by post type, template, specific post/page, page type, post status, user role, taxonomy, attachment type, or menu item).
• Renders front-end forms via `fstn_form()` with server-side submission handling including validation, a honeypot, and rate limiting; the form targets are stored on the server.
• Exposes field values to themes via template/developer functions such as `fstn_get_field()`, `fstn_the_field()` (escaped by default), `fstn_get_fields()`, `fstn_update_field()`, and `fstn_delete_field()`, with support for multiple contexts (post ID, `option`, user, term, or WP objects).
• Supports conditional logic and validation rules for fields, with server-side enforcement (including required fields and constraints like length/range/pattern/format).
• Offers REST API integration by opting field groups into the REST API so values appear on post responses and can be written with proper permissions.
• Includes import/export and developer tooling: duplicate/import/export of groups (JSON/PHP), WP-CLI commands (`wp fstn json status|sync`, `wp fstn mirror rebuild`, `wp fstn table status`), and local JSON syncing for definitions.