### Godot version

4.2.dev 80de898d721f952dac0b102d48bb73d6b02ee1e8

### System information

OpenXR

### Issue description

The Godot 3 OpenXR plugin supported obtaining boundary/guardian information in order to obtain play space logic. While we do have a function in the `XRInterface` in Godot 4 that is supposed to retrieve this information (`get_play_area`) it is not implemented on the Godot 4 `OpenXRInterface`.

This logic needs to be ported.

### Steps to reproduce

Call `get_play_area`, be amazed by it not returning data :P

### Minimal reproduction project

Any XR project.
ERR_FAIL_NULL(openxr_api);
	for (int i = 0; i < p_action_set->actions.size(); i++) {
		Action *action = p_action_set->actions[i];
		openxr_api->action_free(action->action_rid);
		memdelete(action);
	}
	p_action_set->actions.clear();
}
OpenXRInterface::Tracker *OpenXRInterface::find_tracker(const String &p_tracker_name, bool p_create) {
	XRServer *xr_server = XRServer::get_singleton();
	ERR_FAIL_NULL_V(xr_server, nullptr);
	ERR_FAIL_NULL_V(openxr_api, nullptr);
	Tracker *tracker = nullptr;
	for (int i = 0; i < trackers.size(); i++) {
		tracker = trackers[i];
		if (tracker->tracker_name == p_tracker_name) {
			return tracker;
		}
	}
	if (!p_create) {
		return nullptr;
	}
	ERR_FAIL_COND_V(!openxr_api->is_top_level_path_supported(p_tracker_name), nullptr);
	
	RID tracker_rid = openxr_api->tracker_create(p_tracker_name);
	ERR_FAIL_COND_V(tracker_rid.is_null(), nullptr);