fix!: updated chain assets, removed beta-5 network

[petertonysmith94]

Closes #2281

Breaking change

• Chain ID entry for beta5 has been removed, suggest to use testnet.

  // Before
  import { CHAIN_IDS } from 'fuels';
  const beta5 = CHAIN_IDS.fuel.beta5;
  
  // After
  import { CHAIN_IDS } from 'fuels';
  const testnet = CHAIN_IDS.fuel.testnet;

[petertonysmith94]

I had to remove beta-5 as all the chain ID's were 0 (beta-5, devnet and testnet), causing issues with resolving the correct assets.

[fuel-service-user]

✨ A PR has been created under the rc-2432 tag on fuels-wallet repo.
FuelLabs/fuels-wallet#1329

[LuizAsFight]

instead of using a static assets.json , could we have a script that would run post-build ? something like

const devnetProvider = await Provider.create(DEVNET_URL);
const devnetChainId = provider.getChainId();
const devnetBaseAssetId = provider.getBaseAssetId();

const testnetProvider = await Provider.create(TESTNET_URL);
const testnetChainId = provider.getChainId();
const testnetBaseAssetId = provider.getBaseAssetId();

const assets = {
..... // builds the asset structure we have
};

fs.write('assets.json', assets);

[Torres-ssf]

instead of using a static assets.json , could we have a script that would run post-build ? something like

const devnetProvider = await Provider.create(DEVNET_URL);
const devnetChainId = provider.getChainId();
const devnetBaseAssetId = provider.getBaseAssetId();

const testnetProvider = await Provider.create(TESTNET_URL);
const testnetChainId = provider.getChainId();
const testnetBaseAssetId = provider.getBaseAssetId();

const assets = {
..... // builds the asset structure we have
};

fs.write('assets.json', assets);

This would indeed be a good solution for this problem

[petertonysmith94]

instead of using a static assets.json , could we have a script that would run post-build ? something like

const devnetProvider = await Provider.create(DEVNET_URL);
const devnetChainId = provider.getChainId();
const devnetBaseAssetId = provider.getBaseAssetId();

const testnetProvider = await Provider.create(TESTNET_URL);
const testnetChainId = provider.getChainId();
const testnetBaseAssetId = provider.getBaseAssetId();

const assets = {
..... // builds the asset structure we have
};

fs.write('assets.json', assets);

I explored this option and came to conclusion that it might not be the ideal solution.

1. Makes our build dependent on the network (and therefore having an internet connection).
2. We currently export assets and CHAIN_IDS from our fuel package.
3. By only writing to assets.json, we could make the above exports out of sync.

I'm favouring pushing the hard-coded asset ID's for now and have added an e2e-assets test to ensure these values don't go out of sync with the networks.

[github-actions]

Coverage Report:

Lines	Branches	Functions	Statements
45.44%(+0.03%)	38.52%(+0.06%)	42.24%(+0.05%)	45.21%(+0.03%)

Changed Files:

Coverage values did not change👌.