Fixed relevancy ordering for Full-Text

[Hydrocharged]

Fixes dolthub/dolt#6530

[Hydrocharged]

This might be an efficient way to implement the table column requirement for MATCH, but that depends on a big assumption that appears to hold true. While looking through the scope logic, it looked like we always start with the fromScope constructed from the target table, and we then append projected columns, extra columns, etc. onto that initial scope. That leads to the first n columns always being the table columns, in their schema ordering. With that, I can always grab the table row with row[:len(tableSchema)]. This makes everything extremely straightforward, and makes this a relatively small change.

[max-hoffman]

I think this is the right idea. The fromScope cols are the input deps you want. But my first reaction is that this will panic for any queries that use projection pruning. I see that you disable the projection pruning rule for match expressions, so it is a smaller subset of queries will panic -- aggregations and windows. So either 1) we disable aggregation/window mixing with MA, 2) we ship and cut a ticket expecting someone to hit this panic soon, 3) you use the scope extraCols to register MA dependencies and embed those expressions in MatchAgainst for index fixup/execution reference. The projection pruning guard rail is probably unnecessary after (3).

> ALTER TABLE test ADD COLUMN extracol2 INT DEFAULT 7;
> SELECT pk, count(pk), MATCH(doc) AGAINST('aaaa') as relevancy FROM test ORDER BY relevancy DESC;

panic: runtime error: slice bounds out of range [:4] with capacity 3 [recovered]
	panic: runtime error: slice bounds out of range [:4] with capacity 3

goroutine 10 [running]:
testing.tRunner.func1.2({0x1f72700, 0xc00004aa38})
	/usr/local/go/src/testing/testing.go:1545 +0x238
testing.tRunner.func1()
	/usr/local/go/src/testing/testing.go:1548 +0x397
panic({0x1f72700?, 0xc00004aa38?})
	/usr/local/go/src/runtime/panic.go:914 +0x21f
github.com/dolthub/go-mysql-server/sql/expression.(*MatchAgainst).Eval(0xc0004deca8?, 0x3?, {0xc0004f1ad0?, 0x2?, 0xc00065a500?})
	/Users/max-hoffman/go/src/github.com/dolthub/go-mysql-server/sql/expression/matchagainst.go:87 +0x165
github.com/dolthub/go-mysql-server/sql/expression.(*Alias).Eval(0xc00007d7c0?, 0xc00026fb08?, {0xc0004f1ad0?, 0x3?, 0x1e6f8a0?})
...

[Hydrocharged]

A quick stab at #3 didn't lead to much success, so I'll go with #1 for now and make an issue linking to this PR.