That "project manager" and "lead developer" are two separate jobs TO ME sounds like you've got a project manager who isn't doing their damned job.
If they gave you a meaningless title so they can try to use/abuse you for more workload than is reasonable, you're being treated like a fast food worker and not an IT professional -- and I would suggest telling them that in no uncertain terms.
Since at that point you just might be better off flipping burgers for a living. Sometimes it's just not about the money.
Really that you say you're the 'lead developer' but there's also a 'project manager' REEKS of mismanagement and possible incompetence on the part of the latter -- a SIGNIFICANT PART of what you describe as part of your job being what should be theirs.
But then I'm from the age when "project managers" did their huffing job instead of wasting half the day in pointless meetings and the other half playing farmville, all blindly hoping someone else or some sort of software automation like version control will do THEIR JOB for them!
Seriously, of your entire first list, eight of those items should be the Project Manager's responsibility. I mean if all that is on the "lead developer" just what the blazes does their huffing job entail? Brown-nosing everyone in sight to cover up for being unqualified to manage a damned thing?