**Unexpected behavior**
ATTACH PARTITION command fails when destination table's existing partition size is large than `max_partition_size_to_drop`

Attaching a tiny sample of few hundred rows from `db.source_table_sample` to `db.destination_table_full` fails because partition `202108` size is (53.46 GB) which is larger than default `max_partition_size_to_drop` (50GB)

Error message:
```sql
ALTER TABLE db.destination_table_full
    ATTACH PARTITION 202108 FROM db.source_table_sample

Query id: adf2c8fb-ba8a-4846-9c32-fabdb0d387b9


0 rows in set. Elapsed: 0.002 sec.

Received exception from server (version 21.7.11):
Code: 359. DB::Exception: Received from localhost:9440. DB::Exception: Table or Partition in db.destination_table_full was not dropped.
Reason:
1. Size (53.46 GB) is greater than max_[table/partition]_size_to_drop (50.00 GB)
2. File '/drives/ssd1/clickhouse/flags/force_drop_table' intended to force DROP doesn't exist
How to fix this:
1. Either increase (or set to zero) max_[table/partition]_size_to_drop in server config
2. Either create forcing file /drives/ssd1/clickhouse/flags/force_drop_table and make sure that ClickHouse has write permission for it.
Example:
sudo touch '/drives/ssd1/clickhouse/flags/force_drop_table' && sudo chmod 666 '/drives/ssd1/clickhouse/flags/force_drop_table'.
```

However, if I try to do the same in a new empty table `db.destination_table_sample`, it can attach partition successfully.

```sql
ALTER TABLE db.destination_table_sample
    ATTACH PARTITION 202108 FROM db.source_table_sample

Query id: f1567cf5-b1da-476c-aebb-3cf9f767849e

Ok.

0 rows in set. Elapsed: 0.003 sec.
```


How I calculated partition size:
```sql
SELECT
    partition,
    formatReadableSize(sum(bytes_on_disk)),
    round(((sum(bytes_on_disk) / 1000) / 1000) / 1000, 2) AS GB
FROM system.parts
WHERE table = 'destination_table_full'
GROUP BY partition

Query id: 33862450-3dd5-410e-aee0-30fbee339b68

┌─partition─┬─formatReadableSize(sum(bytes_on_disk))─┬────GB─┐
│ 202107    │ 2.07 GiB                               │  2.22 │
│ 202108    │ 49.79 GiB                              │ 53.46 │
│ 202110    │ 5.85 GiB                               │  6.28 │
│ 202109    │ 17.89 GiB                              │ 19.21 │
└───────────┴────────────────────────────────────────┴───────┘
```

**Expected behavior**
Partitions should be attached successfully regardless of `max_partition_size_to_drop` value

**How to reproduce**
ClickHouse server version: ClickHouse server version 21.7.11.3 (official build).
Which interface to use: clickhouse-client (I originally noticed this behavior in the logs of clickhouse-copier)
auto partition_key_columns = metadata.getPartitionKey().column_names;
            Names names_intersection;
            std::set_intersection(columns_to_sum.begin(), columns_to_sum.end(),
                                  partition_key_columns.begin(), partition_key_columns.end(),
                                  std::back_inserter(names_intersection));
            if (!names_intersection.empty())
                throw Exception("Columns: " + boost::algorithm::join(names_intersection, ", ") +
                " listed both in columns to sum and in partition key. That is not allowed.", ErrorCodes::BAD_ARGUMENTS);
        }
    }
    if (mode == MergingParams::Replacing)
        check_version_column(true, "ReplacingMergeTree");
    if (mode == MergingParams::VersionedCollapsing)
    {
        check_sign_column(false, "VersionedCollapsingMergeTree");
        check_version_column(false, "VersionedCollapsingMergeTree");
    }
    
}
DataTypePtr MergeTreeData::getPartitionValueType() const
{
    DataTypePtr partition_value_type;
    auto partition_types = getInMemoryMetadataPtr()->partition_key.sample_block.getDataTypes();
    if (partition_types.empty())
        partition_value_type = std::make_shared<DataTypeUInt8>();
    else
        partition_value_type = std::make_shared<DataTypeTuple>(std::move(partition_types));
    return partition_value_type;
}
Block MergeTreeData::getSampleBlockWithVirtualColumns() const