fix(migrations): improve migration to take @use and @forward into acc

[ChronosSF]

Closes #

Additional information (check all that apply):

• [ ] Bug fix
• [ ] New functionality
• [ ] Documentation
• [ ] Demos
• [ ] CI/CD

Checklist:

• [ ] All relevant tags have been applied to this PR
• [ ] This PR includes unit tests covering all the new code (test guidelines)
• [ ] This PR includes API docs for newly added methods/properties (api docs guidelines)
• [ ] This PR includes feature/README.MD updates for the feature docs
• [ ] This PR includes general feature table updates in the root README.MD
• [ ] This PR includes CHANGELOG.MD updates for newly added functionality
• [ ] This PR contains breaking changes
• [ ] This PR includes ng update migrations for the breaking changes (migrations guidelines)
• [ ] This PR includes behavioral changes and the feature specification has been updated with them

[mddragnev]

Probably if there is a @import at the top, it should stay there too.

[ChronosSF]

Probably if there is a @import at the top, it should stay there too.

Eh not really sure about that... Since it's not a rule to have the imports at the top if I apply the same logic and the last import is somewhere down it might become an issue. What if imports can be put inside css rules too?

[mddragnev]

Probably if there is a @import at the top, it should stay there too.

Eh not really sure about that... Since it's not a rule to have the imports at the top if I apply the same logic and the last import is somewhere down it might become an issue. What if imports can be put inside css rules too?

This is my bad. Because it is invalid to have imports other place than at the top of a css file, yet it is valid in Sass.