An experienced software engineer who could lead a team and set technical guidelines/principles for other team members, who could design complex systems and provide technical solutions for business needs.
A technical resource who could talk to business users(non technical) and can gather requirements and come up with a Statement of Work for his/her company b.y presenting companies product or technical capabilities.
I share your impression. It's a concatenation of two buzzwords that hold unclear meaning. "Solutions" is too vague and associated in my experience with people who want the product without going to the trouble of exploring the problem and clearly specifying it. "Architect" is a title often describing people who stay too far above the reality of implementing the "Solution".
Job ads have a variation of that annoying tendency: javascript ninja, code rockstar ?