fix: [#312] orm connection is not working

[hwbrzzl]

Closes goravel/goravel#312

📑 Description

Solve three problems:

1. Framework can't identify the connection of slice model;
2. Framework can't switch connections when the driver is the same;
3. The conditions will be chaotic when switching connections through the old logic;

✅ Checks

• My pull request adheres to the code style of this project
• My code requires changes to the documentation
• I have updated the documentation as required
• All the tests have passed

ℹ Additional Information

[codecov]

Codecov Report

Attention: 530 lines in your changes are missing coverage. Please review.

Comparison is base (ad61d31) 62.24% compared to head (a5b128e) 70.69%.
Report is 90 commits behind head on v1.13.x.

Files	Patch %	Lines
database/gorm/query.go	82.90%	67 Missing and 39 partials ⚠️
database/gorm/cursor.go	36.44%	65 Missing and 3 partials ⚠️
database/console/seed_command.go	35.93%	35 Missing and 6 partials ⚠️
foundation/container.go	15.55%	38 Missing ⚠️
foundation/application.go	41.17%	22 Missing and 8 partials ⚠️
database/gorm/test_models.go	84.06%	20 Missing and 9 partials ⚠️
database/factory.go	68.60%	18 Missing and 9 partials ⚠️
database/gorm/test_utils.go	91.97%	12 Missing and 3 partials ⚠️
log/formatter/general.go	76.56%	11 Missing and 4 partials ⚠️
database/seeder.go	72.00%	8 Missing and 6 partials ⚠️
... and 26 more

Additional details and impacted files

@@             Coverage Diff             @@
##           v1.13.x     #354      +/-   ##
===========================================
+ Coverage    62.24%   70.69%   +8.45%     
===========================================
  Files          125      145      +20     
  Lines         8078    10138    +2060     
===========================================
+ Hits          5028     7167    +2139     
+ Misses        2717     2522     -195     
- Partials       333      449     +116     

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

[hwbrzzl]

Solve the problem: The conditions will be chaotic when switching connections through the old logic.

Before, the Where method, etc. calls the Gorm method directly and gets a new Gorm instance.

Now, the conditions will be saved in Conditions, and will be built when calling a final method, like: Get.

After this change, we can control the conditions and the Gorm instance more freely.

[hwbrzzl]

There is no changes for this file, just order the methods.

[hwbrzzl]

The buildConditions method will be called when need to call the Gorm method directly.

[hwbrzzl]

After this change, we can set query to a variable and reuse it, such as:

query := facades.Orm().Query().Where("a = b")
query.Where("b = c").Find() == facades.Orm().Query().Where("a = b").Where("b = c").Find()
query.Where("c = d").Find() == facades.Orm().Query().Where("a = b").Where("c = d").Find()

[hwbrzzl]

This is the key that query can be reused: the conditions will be copied when calling conditions methods.

[hwbrzzl]

The original Gorm instance of QueryImpl will not be changed, to avoid the conditions chaotic.

[hwbrzzl]

Fix:

1. Framework can't identify the connection of slice model;
2. Framework can't switch connections when the driver is the same;

[devhaozi]

LGTM