fix: Denial by default to all resources when no permissions set

[jyejare]

What this PR does / why we need it:

We observed Inconsistent permission response behavior across Feature Store API routes.

• Fixing the behaviour by changes in filter_only and named_patterns

Which issue(s) this PR fixes:

Inconsistent permission response behavior across Feature Store API routes. RHOAIENG-35929

Misc

[jameerpathan111]

@jyejare, what do you think about following suggestion?

Suggested change

	if not grant:
	if not filter_only:
	logger.error(f"Permission denied: {','.join(explanations)}")
	raise FeastPermissionError(",".join(explanations))
	elif filter_only and not p.name_patterns:
	logger.error(f"Permission denied: {','.join(explanations)}")
	raise FeastPermissionError(",".join(explanations))
	else:
	continue
	if grant:
	logger.debug(
	f"Permission granted for {type(resource).__name__}:{resource.name}"
	)
	_permitted_resources.append(resource)
	break
	if not grant:
	if filter_only or p.name_patterns:
	continue
	logger.error(f"Permission denied: {','.join(explanations)}")
	raise FeastPermissionError(",".join(explanations))
	logger.debug(
	f"Permission granted for {type(resource).__name__}:{resource.name}"
	)
	_permitted_resources.append(resource)
	break