DLO/SLO segments won't apply headers when upload DLO/SLO with x-delete-at/x-delete-after

if users apply headers x-delete-at/x-delete-after for DLO/SLO, the headers won't apply to DLO/SLO segments, so it leaves all segments in the cluster and never clean up.

$ swift upload test 3M --object-name 3M_object_deleted_in_30s --use-slo -S 1048676 -H 'x-delete-after:30'
3M_object_deleted_in_30s segment 0
3M_object_deleted_in_30s segment 1
3M_object_deleted_in_30s segment 2
3M_object_deleted_in_30s

$ swift stat test 3M_object_deleted_in_30s
              Account: AUTH_demo
            Container: test
               Object: 3M_object_deleted_in_30s
         Content Type: application/octet-stream
       Content Length: 3145728
        Last Modified: Mon, 28 Nov 2016 08:14:48 GMT
                 ETag: "9e8bc43137caef29f5e0b4f85cc849e8"
           Meta Mtime: 1480320571.000000
          X-Delete-At: 1480320917
        Accept-Ranges: bytes
          X-Timestamp: 1480320887.61053
           X-Trans-Id: tx3e6af4ef852c404fb5036-00583be779
X-Static-Large-Object: True

$ swift list test_segments --prefix 3M_object_deleted_in_30s
3M_object_deleted_in_30s/slo/1480320571.000000/3145728/1048676/00000000
3M_object_deleted_in_30s/slo/1480320571.000000/3145728/1048676/00000001
3M_object_deleted_in_30s/slo/1480320571.000000/3145728/1048676/00000002

$ swift stat test_segments 3M_object_deleted_in_30s/slo/1480320571.000000/3145728/1048676/00000000
       Account: AUTH_demo
     Container: test_segments
        Object: 3M_object_deleted_in_30s/slo/1480320571.000000/3145728/1048676/00000000
  Content Type: application/swiftclient-segment
Content Length: 1048676
 Last Modified: Mon, 28 Nov 2016 08:14:45 GMT
          ETag: 690d57b2a2466e0b23d75749c00187d1
 Accept-Ranges: bytes
   X-Timestamp: 1480320884.57216
    X-Trans-Id: tx5b1574a083de4c39ba429-00583be7a7