Use default branch protection defaults

What does this MR do and why?

Use default branch protection defaults

This commit adds using of default_branch_protection_defaults column while creating protected branch

How to set up and validate locally

Protection none

{
"default_branch_protection_defaults": {
        "allowed_to_push": [
            {
                "access_level": 30
            }
        ],
        "allow_force_push": true,
        "allowed_to_merge": [
            {
                "access_level": 30
            }
        ]
    }
}

Protection Partial

{
"default_branch_protection_defaults": {
        "allowed_to_push": [
            {
                "access_level": 30
            }
        ],
        "allow_force_push": false,
        "allowed_to_merge": [
            {
                "access_level": 30
            }
        ]
    }
}

Protected Fully

{
"default_branch_protection_defaults": {
        "allowed_to_push": [
            {
                "access_level": 40
            }
        ],
        "allow_force_push": false,
        "allowed_to_merge": [
            {
                "access_level": 40
            }
        ]
    }
}

Protected Against Developer Pushes

{
"default_branch_protection_defaults": {
        "allowed_to_push": [
            {
                "access_level": 40
            }
        ],
        "allow_force_push": true,
        "allowed_to_merge": [
            {
                "access_level": 30
            }
        ]
    }
}

MR acceptance checklist

This checklist encourages us to confirm any changes have been analyzed to reduce risks in quality, performance, reliability, security, and maintainability.

• I have evaluated the MR acceptance checklist for this MR.

Related to #408152 (closed)