fix: remove false-positive deprecation calls in search methods

The audit script picked up 'settings' and 'context' as method names from
inside an object-literal return value and a JSDoc `@param` block. Those
two methodDeprecationLogger calls were injected into the bodies of
rocketchatSearch.getProvider and rocketchatSearch.search by mistake.
Neither method is a deprecation target.

Author: ggazzo

apps/meteor/app/search/server/methods.ts

@@ -25,7 +25,6 @@ Meteor.methods<ServerMethods>({
 	 * Get the current provider with key, description, resultTemplate, suggestionItemTemplate and settings (as Map)
 	 */
 	'rocketchatSearch.getProvider'() {
-		methodDeprecationLogger.method('settings', '9.0.0', '/v1/settings');
 		const provider = searchProviderService.activeProvider;
 		if (!provider) {
 			return undefined;
@@ -49,7 +48,6 @@ Meteor.methods<ServerMethods>({
 	 * @param payload custom payload (e.g. for paging)
 	 */
 	async 'rocketchatSearch.search'(text, context, payload) {
-		methodDeprecationLogger.method('context', '9.0.0', []);
 		payload = payload !== null ? payload : undefined; // TODO is this cleanup necessary?
 
 		if (!searchProviderService.activeProvider) {