I finally succeeded in reproducing your error

ERROR #5803: Failed to acquire exclusive lock on instance of '%Studio.ProjectItem'

The conditions are somewhat strange and you should take an exact check what applies in your case.
The story:

• ENSEMBLE uses %Studio.Project to manage the export.
• every item to be exported gets locked. The global  name to look for is ^oddPROJECT
• if the number of items exceeds a threshold the whole Project storage will be locked
• this is NOT possible if someone else has any other project in this namespace locked for him
  then the export will fail and you get the ERROR message. 

So try to find out in Terminal

• USER>zn "%SYS"
  %SYS>write $system.SQL.GetLockThreshold()      ; most likely default => 1000
  xxxxxx
• %SYS>d ^LOCKTAB
                     LOCK table entries at
                  16767728 bytes usable, 16774528 bytes available.
  Entry Process     X#   S#Flg   W# Item Locked
     1) 1016         1               ^["^^c:\intersystems\17e20\mgr\"]%SYS("CSP","Daemon")
     2) 6444         1               ^["^^c:\intersystems\17e20\mgr\"]ISC.LMFMON("License Monitor")
     3) 6752         1               ^["^^c:\intersystems\17e20\mgr\"]ISC.Monitor.System
     4) 12180        1               ^["^^c:\intersystems\17e20\mgr\"]TASKMGR
     5) 8568         1               ^["^^c:\intersystems\17e20\mgr\user\"]oddPROJECT("Ali")
   
  Command=>

Look if you see oddPROJECT

Next try to estimate the number of items your production will export.
If you get close to the dimension of  xxxxxx then you run most likely into your error.
Be aware that some components can create more than 1 entry. So your limit might be lower (70% ??)

You can increase the threshold in
MgmtPortal > System Admin > Configuration > SQL and Object Settings > General SQL Settings

ATTENTION:  If you set this value to high you risk an overrun of the LOCKTABLE.
        This blocks the whole instance.   Increasing the size of LOCKTABLE + Restart is then required. Or you set the limit t back.

as you noted SEEMS not to work.

method OnInit() as %Status

This user callback method is called via initConfig() from %OnNew() or in the case of SOAP Services from OnPreSOAP()

 $$$LOGINFO("INIT") translates to
   Do ##class(Ens.Util.Log).LogInfo($$$CurrentClass,$$$CurrentMethod,"INIT")

I'd suggest to replace it by set ^Antonio($i(^Antonio))=$lb($ZDT($h,3),"INIT")

so so find out if your Init gets called or not or multiple times, .. 
Especially during init phase high independence from the rest could be useful

The the description is somewhat vague:

Exclusive LOCK happens on process basis not by user !
It's not clear where you run "export from the production". Portal,Terminal, Studio, ...

if you are in Studio and run "export from the production" in MgmtPortal or Terminal then you have 2 processes.
1 has the lock the other can't get it.
 

take a look in MgmtPortal >  System Operation > Locks  > View Locks

Now you should see who is owning your lock 

BTW. Class %ZEN.Component.querySource  still does it as iit did in past.

For more tricky manipulation you have

/// (optional) Name of Server-side callback method to call to create
/// a <class>%ResultSet</class> object.<br>
/// This must be the name of a server-only method in the page
/// class that contains this component.
Property OnCreateResultSet As %ZEN.Datatype.delegator(FORMALSPEC = "*tSC:%Status,pInfo:%ZEN.Auxiliary.QueryInfo", RETURNTYPE = "%ResultSet");

/// (optional) Name of Server-side callback method to call to execute the
/// <class>%ResultSet</class> object.<br>
/// This must be the name of a server-only method in the page
/// class that contains this table pane.
Property OnExecuteResultSet As %ZEN.Datatype.delegator(FORMALSPEC = "pRS:%Library.ResultSet,*tSC:%Status,pInfo:%ZEN.Auxiliary.QueryInfo", RETURNTYPE = "%Boolean");