You may not know all the reasons for doing this. We had to adopt similar types of things because they were required for a certification required by our clients. If this is the case that these procedures were adopted for a contractual or regulatory reason, there is zero chance of overturning them.
However, what is of most concern is that you document the impact of performing these procedures on deadlines and project work. Once the full cost in time is known, then, if they are not contractual, you will have the evidence you need to persuade them to consider loosening them. Moreover, if your clients are upset that their deadlines are being moved due to these procedures, you have someone who will take your side against management and the users of your software are far more likely to be effective in pushing back on something like this. You cannot hope to reverse a decision of this nature without allies among your users since you do internal applications. But to get to this point, you need to fully implement the new procedures and document the delays caused in other work. When you do time estimates, make sure you allow for that work as part of the project (and make it a separate line item, clearly visible, when you do). Your project owners may find that they don't want to spend an additional 40% of the time on each project and push back the requirement themselves. This is the most effective way to push back. Remember these testing items are project costs and need to be billed internally to the projects you are responsible for. Let the extra cost and deadlines moved out to speak for themselves.
Even if there is no chance that these requirements will be pushed back, your internal clients need to be aware of the impact on your work. Further, this is a time when you should not be working extra to avoid having those deadlines slip. There is a cost to time-consuming new procedures and the organization must be made aware of that cost by letting things slip because you do not have time to do them.
Remember it is not your place to dictate to management what you want to do, it is your place to do what they are paying you to do and they get to decide if a process is what they want you to spend your time on because they are paying your salary. Yes you can move on, but honestly, in this case, you will find yourself moving on fairly frequently.
In your career, you will often have to perform functions you don't want to do. The next job will have other functions you don't want to do as well. Some of this is pretty much inherent in all jobs. It is unrealistic to expect to spend 100% of your time (or even the majority of time) coding at most places. The business is in business to make a profit, there are more important things to the business than writing code. Just because those things are not personally important to you (or uninteresting) doesn't negate the fact that they are important to the business.
If you want to do only the things you want to do, then start your own business. You, of course, will likely find that there are plenty of things you need to do when you own a business that aren't fun and exciting like taxes and accounting and marketing, etc.