REST API Write access - Fix invalid default value

[JoryHogeveen]

Description

De default value for the write_all option of a Pod was set to the Pod name. This results in incorrect parsing of a boolean in PodsRESTFields::field_allowed_to_extend() in write mode.

@sc0ttkclark See testing instructions. I'm not sure how you would like to implement something that will repair old Pods. You could check for ! empty() instead of using filter_var() but that might not be desirable.

Related GitHub issue(s)

Fixes #7327

Testing instructions

1. Create a Pod without this patch and enable write mode.
2. Go to PodsRESTFields::field_allowed_to_extend() and dump $all_fields_can_use_mode. It will return false, allways.
3. Verify with $pod->get_arg( $pod_mode_arg, 'value_not_set' ) and see it returns the Pod name instead of a 1 or 0.
4. Apply this patch
5. Disable REST write access and save Pod (important, otherwise it won't reset the value)
6. Re-enable REST Write access and save Pod.
7. Redo 1, 2 and 3 and you'll see it returns the correct values now.

PR checklist

• I have tested my own code to confirm it works as I intended.
• My code follows the WordPress Coding Standards.
• My code follows the WordPress Inline Documentation Standards.

[what-the-diff]

PR Summary

• Enhancements in REST API Options
  Several modifications took place in the set of options available for interacting with the REST API. This consists of alterations to the rest_base that allows customized endpoints, rest_namespace for custom namespace definitions, read_all and read_all_access for advanced viewing capabilities, write_all to allow updates over all fields, and rest_api_field_mode & rest_api_field_location for advanced field handling. The changes enhance the flexibility and control of API calls made to the service.

• Bug Fix in PodsRESTFields.php
  The PR also includes a crucial bug fix for versions of Pods before 3.2.7. Previously, the default value for 'pod_mode' was incorrectly assigned to the pod name. This issue is now rectified with the update. This bug fix will improve reliability and prevent misbehavior in the application's function.

[PodsBot]

[phpcs] _{reported by reviewdog 🐶}
WordPress.Arrays.ArrayDeclarationSpacing.AssociativeArrayFound
When a multi-item array uses associative keys, each value should start on a new line.

[JoryHogeveen]

@sc0ttkclark This is throughout the whole array, want me to fix or leave as is?

[sc0ttkclark]

The phpcs stuff is just optional to fix. Autoformat can help but it's file by file as we're able to.

The base branch was changed.

[sc0ttkclark]

Added backcompat handling but did not include a DB migration.