Feat/forbidden flags

[ben-pr-p]

This implements forbidden flags as per #118.

As far as I can tell by running and rerunning the perfTest at various stages of development and at the end, this has no impact on performance for users who choose not to use the feature.

Right now, 14.9.6 is failing with a Postgresql syntax error - do you know if there is something funky with pg going on in that version?

[benjie]

Suggested change

	}
	flagsToSkip = await forbiddenFlagsResult;
	} else {
	flagsToSkip = await forbiddenFlagsResult;
	}

[benjie]

Right now, 14.9.6 is failing with a Postgresql syntax error - do you know if there is something funky with pg going on in that version?

Could it be that it's actually PostgreSQL 9.6 kicking out the syntax somewhere? The PR's a little too large for me to quickly scan it and spot the issue.

pg and Node 14 did have weird interactions for a while, but I've only seen it "hanging" rather than giving syntax errors.

I really need to track a version of the PostgreSQL schema in version control so I can track the actual diff.

(I don't have time to fully review this today, but if we can get this and #129 approved I'll merge them into a single migration manually later.)

[benjie]

I don't have write permission to this branch; please merge my changes from this branch:

https://github.com/graphile/worker/tree/feat/forbidden-flags

(I merged the latest main branch, plus I re-ordered all the forbidden_flags parameters so that they go at the end of the arguments lists so that the changes are non-breaking for people using positional rather than named arguments.)

[benjie]

I've pushed a huge chunk more work to feat/forbidden-flags

[benjie]

The syntax error was indeed a PG9.6 issue; drop function foo; is not supported - you have to supply the argument types.

[benjie]

(More work on the other branch.)

[ben-pr-p]

Closing in favor of #131