Fixed bug with matching default table with alias

[Zhaars]

Currently, Acra expects that columns in SELECT statement haven't been aliased if FROM has a non-aliased table or they should have proper alias. But databases allow specific alias for table but use columns without an alias.

So if the query contains Columns without aliases and the table is aliased, Acra should consider this table as default. Added checking for containing aliases in tables expressions and switch between extracting tables functions depending on queries.

Checklist

• [ ] Change is covered by automated tests
• [ ] The coding guidelines are followed
• [ ] Public API has proper documentation in the Acra documentation site or has PR on documentation repository with new changes
• [ ] CHANGELOG.md is updated (in case of notable or breaking changes)
• [ ] CHANGELOG_DEV.md is updated
• [ ] Benchmark results are attached (if applicable)
• are up-to-date (in case of API changes)