MB-52109 Do not use round robin planner in serverless deployment

If the planner gives error, it is returned to the user. There is no
fallback on round robin planner as it can break the tenant
affinity/sub-clustering.

Change-Id: I4e08d3951a2aba616dc7d56bd7c0a53065241f48

secondary/manager/client/metadata_provider.go

@@ -1309,8 +1309,8 @@ func (o *MetadataProvider) recoverableCreateIndex(idxDefn *c.IndexDefn,
 		}
 	} else {
 		layout, definitions, err = o.plan(idxDefn, plan, watcherMap, allowLostReplica, actualNumReplica, enforceLimits)
-		//DEEPK add error here for resource limit reached
-		if err != nil && (strings.Contains(err.Error(), "Index already exist") || strings.Contains(err.Error(), c.ErrIndexScopeLimitReached.Error()) || strings.Contains(err.Error(), c.ErrIndexBucketLimitReached.Error())) {
+
+		if err != nil && (c.IsServerlessDeployment() || (strings.Contains(err.Error(), "Index already exist") || strings.Contains(err.Error(), c.ErrIndexScopeLimitReached.Error()) || strings.Contains(err.Error(), c.ErrIndexBucketLimitReached.Error()))) {
 			o.cancelPrepareIndexRequest(idxDefn.DefnId, watcherMap)
 			return err
 		}