(core) Don't throw error in onRecord(s) for insufficient access for includeColumns

Summary:
This removes checking for full access in `onRecord/onRecords` when `includeColumns` is a non-default value. The check had two problems:

1. It relied on the access level being present in the URL query parameters, which doesn't work if the page has redirected. See the discussion in https://grist.slack.com/archives/C0234CPPXPA/p1702576602615509. There seems to be no way to reliably and synchronously check the access level.
2. Calling `onRecords` before `ready` and forgetting to handle an error from the access check meant that `ready` wouldn't be called, so Grist couldn't request the correct access level from the user. I made this mistake and it seems like a nasty footgun.

Ultimately this has no effect on security, as an error will still be raised, but in a place where the widget developer can't catch it. They'll still see an error message in the console, and they can still check the access level reliably using `onOptions`, so I think this is OK.

Test Plan: Updated nbrowser test

Reviewers: georgegevoian, paulfitz

Reviewed By: georgegevoian, paulfitz

Differential Revision: https://phab.getgrist.com/D4145

app/client/components/WidgetFrame.ts

@@ -489,7 +489,9 @@ export class GristViewImpl implements GristView {
     // These options are newer and expose more data than the user may have intended,
     // so they require full access.
     if (this._access !== AccessLevel.full) {
-      throwError(this._access);
+      throw new Error(
+        `Setting includeColumns to ${options.includeColumns} requires full access.` +
+        ` Current access level is ${this._access}`);
     }
     if (options.includeColumns === 'normal') {
       // Return all 'normal' columns of the table, regardless of whether the user has shown them.