But it is also perfectly possible to achieve good perception, strong connections, lots of face time, and ability to handle office issues, while also being really bad at your actual job, and without any of the positives you mention (except for the fairly bland "easy to get along with").
The real problem, of course, is that what office politics optimize for is extraversion over performance, so anyone who's introverted (which a disproportionate number of programmers still are) is going to come in at a disadvantage.
And, um...if you're writing the code that's required of you, by the people who require it, and you're writing it well and in a timely fashion, it doesn't matter if you brag about it to everyone around, it's plenty useful to the company. I don't know where you've worked where the primary work you've done has been code that you've come up with on your own, which you've then had to "sell" to your own bosses and coworkers, but that's definitely not the norm.
Second of all, you seem to be looking at things in very black and white terms. Of course you need to be able to communicate project requirements and dependencies and whatnot, both within and between teams. That's nowhere near the same thing as "networking" or "making connections" in the commonly-understood sense, which is much more about going over to have a chat and a laugh with Steve or Patty down the hall...or, to take it a step further, going out for a game of golf and running into the CTO there, and just happening to have a chat about your upcoming review.
So, in short: yes, of course "being good at your job" requires communication and people skills, as well as (in our case) coding skills. But there are many places where the skills required to advance—both financially and in your career—are exclusively the people skills, regardless of the fact that the skills that are primarily relevant to job performance are the coding skills. This creates perverse incentives, results in unqualified people getting managerial positions, and massively disadvantages those who genuinely care more about doing a good job than "selling themselves"—especially introverted people—in the workplace.
This is not about spending time chatting up people all around the office and networking. It's about responding clearly when people ask you questions, when you have your 1:1 with your manager, and in how you write your emails, etc.
And saying that if no one knows about you you should be paid less is so false. Because, everyone will know about you when you leave and things stop working. Im not talking about single point of failure. But say all non communicating developers are gone from software company one day, id say company would feel that.
Perception = you are good at communicating your work to others
Connections = you have a strong network and stay informed and know who to talk to for different tasks
Face time = you are easy to get along with
Ability to handle office issues = you are a lubricant that make the group dynamic work
If you don't do those things, then you could write fantastic code, but: no one will know about it, know to ask you about it, be aware you're doing it, and find you somewhat of a drag on the office atmosphere. Basically, your work is not useful to the company that is paying you, and you should be paid less because of this.