[Feature Request] 添加配置可开启内嵌视图后进行的where尽量内置（只针对简单的别名和and查询）

[xingyunxing]

如easyEntityQuery.queryable(BlogEntity.class)
.leftJoin(Topic.class, (t_blog, t_topic) -> t_blog.id().eq(t_topic.id()))
.select((t_blog, t_topic) -> new TopicAndBlogVOProxy()
.column1().set(t_blog.title()) //列1
.column2().set(t_topic.title()) //列2
)
.where(o -> o.column1().eq("3"))
.toList();
原来生成的是
select column1,column2 from (SELECT
t.title AS column1,
t1.title AS column2
FROM
t_blog t
LEFT JOIN
t_topic t1
ON t.id = t1.id )
where column1 = '3'

如果开启where内置期望生成 select column1,column2 from (SELECT
t.title AS column1,
t1.title AS column2
FROM
t_blog t
LEFT JOIN
t_topic t1
ON t.id = t1.id
where t.title = '3') t

[xuejmnet]

@xingyunxing 升级到3.1.0

        easyEntityQuery.queryable(SysUser.class)
                .configure(s->s.getBehavior().add(EasyBehaviorEnum.SMART_PREDICATE))//这句
                .innerJoin(SysBankCard.class, (user, bank_card) -> user.id().eq(bank_card.uid()))
                .select((user, bank_card) -> new UserBankDTO2Proxy()
                        .name().set(user.name())
                        .phone().set(user.phone())
                        .code2().set(bank_card.code())
                ).where(u -> {
                    u.code2().eq("123");

                    u.or(()->{
                        u.name().eq("name");
                        u.phone().eq("phone");
                    });
                })
                .toList();

则可以尽可能往前一步进行where穿透

SELECT t2.`name` AS `name`, t2.`phone` AS `phone`, t2.`code2` AS `code2`
FROM (
	SELECT t.`name` AS `name`, t.`phone` AS `phone`, t1.`code` AS `code2`
	FROM `t_sys_user` t
		INNER JOIN `t_bank_card` t1 ON t.`id` = t1.`uid`
	WHERE t1.`code` = '123'
		AND (t.`name` = 'name'
			OR t.`phone` = 'phone')
) t2
WHERE t2.`code2` = '123'
	AND (t2.`name` = 'name'
		OR t2.`phone` = 'phone')