Skip hooks when pushing security branches with secpick

What does this MR do?

This prevents hook execution when creating backports.

This is safe because we know that we are pushing to security.

This is beneficial, since hooks may fail (if set up with lefthook) if the origin/master and security/master are very different.

As an internal developer-facing change, no changelog trailer is required.

Does this MR meet the acceptance criteria?

Conformity

• I have included changelog trailers, or none are needed. (Does this MR need a changelog?)
• I have added/updated documentation, or it's not needed. (Is documentation required?)
• I have properly separated EE content from FOSS, or this MR is FOSS only. (Where should EE code go?)
• I have added information for database reviewers in the MR description, or it's not needed. (Does this MR have database related changes?)
• I have self-reviewed this MR per code review guidelines.
• This MR does not harm performance, or I have asked a reviewer to help assess the performance impact. (Merge request performance guidelines)
• I have followed the style guides.
• This change is backwards compatible across updates, or this does not apply.

Availability and Testing

• I have tested the functionality of this MR