This is error is somewhat unexpected. I though shrink was only moving entire pages around, but it seems that I was wrong.
I'm also inclined to think that it is a bug that you get this error, but I would not expect Microsoft to fix it. So it is time for a plan B.
You first need to determine which table that is on this page. If you are on SQL 2019 or later, run this query:
SELECT pi.object_id, s.name, o.name
FROM sys.dm_db_page_info(db_id('YourDB'), 1, 134083999, DEFAULT) pi
JOIN sys.all_objects o ON pi.object_id = o.object_id
JOIN sys.schemas s ON o.schema_id = s.schema_id
On older versions run
DBCC TRACEON (3604)
DECLARE @dbid int = db_id('YourDB')
DBCC PAGE(@dbid, 1,134083999)
And then look for ObjectID in the output and translate to a table name,
Once you have the table, verify that this is a wide table where the total column size can exceed 8060. Then you will need to decide what to do with it. Maybe copy it to another database with SELECT INTO, then truncate it the actual database, proceed with the shrink and copy data back. I would try this on a backup of the database first.