Asset version updates with different file names

Today: 

• In the web UI, to create a new version of an existing asset, the uploaded file must have the same filename in the same folder.
• If the filename is different, AEM treats it as a new, separate asset, not as a version.

Desired behaviour:

• New versions of an asset can be added regardless of the file name, e.g. by selecting the asset and clicking “add new version”.

Reasoning:

• Updated files often come with new names but should still be stored as versions of existing assets. E.g. if a legacy asset was uploaded (or migrated from our old DAM) with the file name: coporate-presentation-2022-v1.ppt, I want to be able to upload a new version that is called hbk-coporate-presentation-2026.ppt
• We are not starting a DAM from scratch or renaming 30,000 files. That means that even though we can update to newer versions in AEM Assets, any errors, bad naming or typos in old file names get carried over into the new version.
• When users download the updated file, it has the file name of the first version, e.g. coporate-presentation-2022-v1.ppt, even though it is the 2026 version. That is confusing and unacceptable.