fix(db|tmp): CustomPrismaClient issue

Incorrect temptation to import the default client instead of utilizing the provided custom client.
**This solution is temporary!** Until nestjs-prisma new release.

Related Links to the issue:
- notiz-dev/nestjs-prisma#79

api/src/app/app.module.ts

@@ -1,6 +1,6 @@
 import { Module } from '@nestjs/common';
 
-import { CustomPrismaModule } from 'nestjs-prisma';
+import { CustomPrismaModule } from 'nestjs-prisma/dist/custom';
 import { AppController } from './app.controller';
 import { AppService } from './app.service';
 import { MusicModule } from '../music/music.module';
@@ -20,4 +20,4 @@ import { ConfigModule } from '@nestjs/config';
   controllers: [AppController],
   providers: [AppService],
 })
-export class AppModule {}
+export class AppModule { }

api/src/music/music.service.ts

@@ -1,13 +1,13 @@
 import { Injectable, Inject } from '@nestjs/common';
-import { CustomPrismaService } from 'nestjs-prisma';
+import { CustomPrismaService } from 'nestjs-prisma/dist/custom';
 import { Prisma, Music, PrismaClient } from '@musica/data-access/client';
 
 @Injectable()
 export class MusicService {
   constructor(
     @Inject('DataAccessService')
     private prisma: CustomPrismaService<PrismaClient>
-  ) {}
+  ) { }
 
   create(data: Prisma.MusicCreateInput) {
     return this.prisma.client.music.create({ data });