I used to work in PreSales. I worked with lots of people who were ex SWEs/SRE/insertTechTitleHere who transitioned into PreSales/Solution Architects (SAs). At least a few of them did this by first doing an internal transition into a PreSales role so they could get customer facing experience.

With regards to Developer Relations versus PreSales, you should ask yourself what you want to focus on. Do you want to work with customers on actual use cases (usually POCs) and show them how your company's product will address their use case? Then it's PreSales/SA. Do you want to evangelize a product more broadly? Then it's Developer Relations.

Regarding PreSales, I would really recommend you evaluate if you want to stay technical or not. Some products require PreSales and SAs to be quite technical. Other products really need a sales person who understands when to say "Oh yes, we expose our database through JDBC or a RESTful call" and maybe walk through how that is done - but nothing really all that much beyond talking. So it's important to make sure you pick a role that fits what you want.

Given that you have a strong technical background, I'd recommend you find a role that can utilize your understanding of technical matters. It's a good differentiator. Lots of PreSales/SA folks aren't that technical outside of talking the talk.