Too many address-related APIs lead to confusion

[homura]

There has been a breaking change in the address format in Lumos's address-related API, specifically at CKB2021. This change involved the encoding method and rule. Lumos has added a new method called encodeToAddress to encode a script to a CKB2021 address. Previously, there were multiple address encoding and decoding methods in Lumos. Currently, the following address-related APIs are available in @ckb-lumos/helpers:

Name	Status	Description
generatePredefinedAddress	deprecated	Script -> Address(CKB2019 only)
generateSecp256k1Blake160Address	deprecated	Script -> Address(CKB2019 only)
generateAddress	deprecated	Script -> Address(CKB2019 only)
scriptToAddress	deprecated	Script -> Address(CKB2019 only)
generateSecp256k1Blake160MultisigAddress	deprecated	Script -> Address(CKB2019 only)
encodeToAddress	activated	Script -> Address(CKB2021 only)
encodeToConfigAddress	activated	Script -> Address(CKB2021 only)
parseAddress	activated	Address -> Script
addressToScript	activated	Address -> Script

Lumos should simplify the address encoding/decoding and reduce developer confusion.