Ticket 49374 -  server fails to start because maxdisksize is recognized incorrectly
    
    Bug Description:  When directly editting dse.ldif, the server had a check
                      when setting the log maxdiskspace vs maxlogsize.  If the
                      maxlogsize is processed first and it is higher than the
                      default maxdisksspace then it throw an error and the server
                      fails to start.
    
                      If you attempt this same operation using ldapmodify it
                      works as "live" updates check all the mods first, so the
                      order of the attributes does not matter.
    
    Fix description:  Remove the size checks from the attribute set function.
                      It is technically redundant since it is correctly checked
                      by the configdse code.
    
    https://pagure.io/389-ds-base/issue/49374
    
    Reviewed by: tbordaz(Thanks!)
    
    (cherry picked from commit 63a0a59c9b09af08151831209ee6711b4363aee2)