Fix MySQL search_RMTObject and search_RMCObject end-to-end

[patrickoshaughnessey]

Summary

Four related bugs prevented every RMTObject:search and RMCObject:search
call from succeeding on MySQL deployments. This PR fixes all four at the
source level so neither proc requires special sql_mode or session
collation at deploy time. SQL_Server versions are unchanged — their
T-SQL equivalents already work correctly.

The four bugs (in order of when they surface)

1. Param-count mismatch — caught at protocol parse

The framework calls every proc as:

CALL <proc>(sIPAddress, twRPersonaIx, ...aData..., @result);
SELECT @result AS result;

That is 2 + len(aData) + 1 = 8 args for these search procs. Both procs
were declared with 7 IN params and 0 OUT params, so MySQL rejected every
call with:

Incorrect number of arguments for PROCEDURE <schema>.search_RMTObject;
expected 7, got 8
(mysql2 errno 1318, sqlState 42000)

Fix: add OUT nResult BIGINT to both procs (matches the convention
used by every other MySQL get_* / set_* proc in this repo) and assign
nResult at the end with the canonical formula

SET nResult = bCommit - 1 - nError;

(same as get_RMTObject_Update, get_RMRoot_Update, set_RMTObject_Type,
etc.). In search_RMCObject, replace the dead
SET nError = bCommit - bError - 1; line — assigned to a local that
nothing reads, clearly meant to be the missing OUT assignment — with the
canonical nResult assignment.

2. bError NULL init — would prevent success branch even after #1

Both procs declared bError INT without a DEFAULT, so bError started
as NULL. The expression IF bError = 0 then evaluated to NULL (falsy
in MySQL), making the success branch unreachable on the happy path:
every call would have fallen through to call_Error
('twRMTObjectIx is invalid' / 'twRMCObjectIx is invalid') even with
valid input. SQL_Server versions already declared @bError INT = 0, so
this was MySQL-only.

Fix: add DEFAULT 0 to bError declaration in both procs, matching
the adjacent bCommit / nError declarations and the SQL_Server
convention. Also added DEFAULT 0 to nError in search_RMTObject for
consistency (search_RMCObject already had it).

3. TRIM ( with space requires IGNORE_SPACE in sql_mode

The proc body had TRIM (IFNULL (sText, '')) (note the space after
TRIM). Without IGNORE_SPACE in the routine's stored sql_mode,
MySQL parses TRIM ( as a user-defined function call, and the call
fails at runtime with:

ERROR 1630: FUNCTION <schema>.TRIM does not exist

This made deployment of the procs sql_mode-dependent (works only when
the session that runs CREATE PROCEDURE happens to have IGNORE_SPACE
set).

Fix: remove the space in TRIM and IFNULL: TRIM(IFNULL(sText, '')).
Now the proc parses correctly under any sql_mode. (Other functions
like POW (, IF (, ArcLength ( do not have this issue and were left
unchanged for minimal diff — TRIM is one of the specific built-ins for
which MySQL's parser distinguishes a user-defined call from the built-in
based on whitespace, when IGNORE_SPACE is off.)

4. Collation mismatch on LIKE — would prevent body execution

The proc body did:

WHERE o.Name_wsRMTObjectId LIKE CONCAT(sText, '%')

The column Name_wsRMTObjectId carries utf8mb4_unicode_ci (declared
on the table) while parameter sText inherits the database's
DEFAULT_COLLATION (typically utf8mb4_0900_ai_ci on MySQL 8). Mixing
two IMPLICIT collations of different names raises:

ERROR 1267: Illegal mix of collations
(utf8mb4_unicode_ci,IMPLICIT) and (utf8mb4_0900_ai_ci,IMPLICIT)
for operation 'like'

Fix: add explicit COLLATE utf8mb4_unicode_ci on the LIKE expression
to force the comparison to the column's collation. EXPLICIT collation
trumps any IMPLICIT operand, so the LIKE works regardless of the database
default collation.

Verification

End-to-end CALL on a MySQL 8 instance with the default session
sql_mode (no IGNORE_SPACE) and default database collation
(utf8mb4_0900_ai_ci), against a table whose name column is
utf8mb4_unicode_ci, completes with @r = 0 (success).

Bug fixed up to	Failure mode
(none)	expected 7, got 8 (errno 1318)
#1, #2	FUNCTION <schema>.TRIM does not exist (errno 1630)
#1, #2, #3	Illegal mix of collations ... for operation 'like' (errno 1267)
#1–#4 (this PR)	clean: nResult = 0, results returned